Dynamic package version numbers with Autoconf and Automake (was: Re: Automake 1.12.0b test release)

2012-08-14 Thread Stefano Lattarini
Hi Bob, I managed to find your old message about dynamically computing package versions for Automake and Autoconf. Some initial comments follows. I'm adding the Autoconf list in CC:, because I believe this is an Autoconf issue more than an Automake one. On 05/20/2012 12:59 AM, Bob Friesenhahn

Re: Dynamic package version numbers with Autoconf and Automake (was: Re: Automake 1.12.0b test release)

2012-08-14 Thread Bob Friesenhahn
On Wed, 15 Aug 2012, Stefano Lattarini wrote: AM_INIT_AUTOMAKE($PACKAGE_NAME,${PACKAGE_VERSION}${PACKAGE_VERSION_ADDENDUM}, ' ') The reason is because it avoids needing to edit configure.ac (a really stupid practice) I agree with this; with today's DVCS, it's very tempting (and IMHO useful)

Re: Dynamic package version numbers with Autoconf and Automake (was: Re: Automake 1.12.0b test release)

2012-08-14 Thread Bob Friesenhahn
The script I intend to use to obtain package information is in the GraphicsMagick repository and produces information gleaned from a 'version.sh' script which has the smarts to produce some obvious variable names. echo `./scripts/pkginfo.sh package_bugreport`

Re: Dynamic package version numbers with Autoconf and Automake

2012-08-14 Thread Miles Bader
Stefano Lattarini stefano.lattar...@gmail.com writes: Actually, it depends. Where and why do you use such dynamically-computed version number in exactly? That seems the real question. My own method is to have: (1) The primary version number is based on VCS info (this is obviously