Version strings

Gary E. Miller gem at
Mon Jan 8 21:34:07 UTC 2018

Yo Hal!

On Mon, 08 Jan 2018 13:14:49 -0800
Hal Murray via devel <devel at> wrote:

> There was similar discussion of waf editing man pages to get the date
> on the bottom left corner.


> I don't understand waf well enough to go there.

Ditto, and not high enough on my list to work on.
> I think this branch of the thread started when you wanted to be able
> to run ntplogtemp directly rather than running it out of
> build/main/ntpclients/

Uh, not me.  A few people complained on devel@

> I don't see any need to link the version of things like simple
> logging scripts to the main ntpsec versions.

And in fact, there is a downside in added complexity and confusion factor.

> Maybe it's time to move ntpviz and the logging stuff to a separate
> package.

How does that help?

> > Yeah, because you have the NTPsec python library installed
> > somewhere.  
> So it's printing the library version rather than its version.

It gets worse, I just updated my git head, reinstalled, my version still says:

ntplogtemp ntpsec-1.0.1+221 2018-01-02T18:30:45Z

So the version updating is broken.

> If waf did edit a local version string, we could add a sanity check
> to verify that a top level program was running with a new-enough
> version of the library.


Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at  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: <>

More information about the devel mailing list