ntpq change in behaviour

[Achim Gratz]

Hal Murray via devel writes:
> I think there are 2 cases for the version string I'd like.
>
> If I have made local edits, I want the build date.  That's the best summary of 
> the edits I've made.

Git describe already tells you if you have uncommited local edits, by
adding "-dirty" at the end.  If you want or need to get more fancy, you
can come up with your own git describe format string, however the more
you deviate from the default pattern the more explanation things need.

> If I have a clean clone I want the git tag.  If I have a tarball, I want 
> whatever the tarball provides.

The tarball should provide the info for the git commit it was cut from,
plus maybe a "-tar" suffix to indicate the actual vintage.  I#ve done
that for other project simply so that after seeing that in bug reports I
don't tell people who don't use git to do something with git.

> If you hang out with geeks in this area, they want to know everything: the 
> version of the compiler, the compiler flags, ... the OS the compiler is 
> running on...  as well as the parameters to configure.  That ends up with the 
> version string being a tag for a slot in a database.

If I need to know that, there's a cache file from configure somewhere
that has all that information.  If that's gone I re-configure.  Most of
this info really doesn't belong into the build product, especially if
you want to have reproducible builds.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada