Old cruft

Gary E. Miller gem at rellim.com
Sat Dec 9 02:11:04 UTC 2017

Yo Hal!

On Fri, 08 Dec 2017 17:24:46 -0800
Hal Murray via devel <devel at ntpsec.org> wrote:

> Found it.  There was an old ntpc.so
> in /usr/local/lib/python2.7/dist-packages/ while new stuff was
> getting installed in /usr/local/lib/python2.7/site-package s/ntp/

Since you have dist-packages, you must be on a Debian, or Debian
derived sitribution.

So then this becomes relevant:


    From the Debian Python Wiki:

        dist-packages instead of site-packages. Third party Python
        software installed from Debian packages goes into dist-packages,
        not site-packages. This is to reduce conflict between the system
        Python, and any from-source Python build you might install

    This means that if you manually install Python from source, it
    uses the site-packages directory. This allows you to keep the two
    installations separate, especially since Debian and Ubuntu rely on
    the system version of Python for many system utilities.

I assuming you did a test of the debian package install, and that properly
installed into:


Then you did a native NTPsec install, and that properly installed here:


Are my assumptions correct?  If so, everything worked as it should.

The only tweak maybe worth adding would be for the NTPsec native install
process check the system for other copies installed in other places.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20171208/e03efc7d/attachment.bin>

More information about the devel mailing list