Re: Resolution of the library-path mess

2017-10-02 Thread Eric S. Raymond via devel
Hal Murray : > >> Do we need a way to check that we are using the right library? > > >> I think that means we need the version string or time stamp in both the > >> library and the code that uses the library with a simple sanity check at > the > >> top of the uses code. > > > It's not normal pr

Re: Resolution of the library-path mess

2017-10-02 Thread Hal Murray via devel
>> Do we need a way to check that we are using the right library? >> I think that means we need the version string or time stamp in both the >> library and the code that uses the library with a simple sanity check at the >> top of the uses code. > It's not normal practice to do this in Python.

Nailing an elusive unicode bug, and a heads up

2017-10-02 Thread Ian Bruene via devel
Several months ago when I added the unit display feature there was a bug that caused ntpq to crash with a unicode error for no apparent reason. The crash was never replicated, but I added some debugging statements in hope of catching it. Someday. In the last week during the release delay Gar

Re: Resolution of the library-path mess

2017-10-02 Thread Eric S. Raymond via devel
Hal Murray : > > > There are two cases. User-installed code and binaries are supposed to go > > under /usr/local/X; stuff from packages goes under /usr/X, where X = {bin, > > lib}. > > I think that means our normal devel-mode install is "user-installed code". Correct. > I think that needs t