Tim,
> Am I correct in thinking that version numbers should only appear once and
> only in AC_INIT?
That's correct.
Some current makefiles maintain a `library version number', different
from the package version number, but I haven't yet seen one use it.
> Are we meant to be using more "standard" version number
> of 3.2.6 or is the 3.2-6 variant still acceptable?
Configure doesn't care. I tend to use m.n-r because I think it's
conventional, but I'm not massively committed to it, and the macros
below don't care -- they extract the first three [0-9]* from the
version number. That's potentially a problem if we want to
distinguish version 1.2-alpha3 from 1.2-beta3 from 1.2-3, but I very
much doubt that we do.
> Does configure provide
> standard defines for getting the major/minor/patch versions (which we can
> then place in the standard C include files that are installed)?
Standard configure currently substitutes PACKAGE_VERSION. The extra
macros define and substitute PACKAGE_VERSION_INTEGER which is
major*1000000 + minor*1000 + release. They also (as of 10 minutes ago)
define PACKAGE_VERSION_{MAJOR,MINOR,RELEASE} and substitute them.
These are substituted, but not put into config.h. At present, I see
them being used by being substituted into a version.h.in or something,
but if there was a consensus that it would be useful, I could put them
into config.h also.
I've updated SSN/78 to mention these.
Norman
--
---------------------------------------------------------------------------
Norman Gray http://www.astro.gla.ac.uk/users/norman/
Physics and Astronomy, University of Glasgow, UK [log in to unmask]
|