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

2012-08-15 Thread Roger Leigh
On Tue, Aug 14, 2012 at 06:57:02PM -0500, Bob Friesenhahn wrote: > AC_INIT(m4_esyscmd([scripts/pkginfo.sh package_name]), > m4_esyscmd([scripts/pkginfo.sh package_version]), > m4_esyscmd([scripts/pkginfo.sh package_bugreport])) > > Unfortunately, the values passed to AC_INIT are ca

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` graphicsmagick-b...@lists.sourcefo

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)

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: Automake 1.12.0b test release

2012-05-23 Thread Stefano Lattarini
On 05/20/2012 10:38 PM, Bob Friesenhahn wrote: > On Sun, 20 May 2012, Stefano Lattarini wrote: >>> >>> What is the workaround for this? >>> >> Yes: the version-generating script should be executed at autoconf runtime >> instead; >> here is what GNU coreutils does, for example: >> >> AC_INIT([GNU

Re: Automake 1.12.0b test release

2012-05-20 Thread Bob Friesenhahn
I got AC_INIT dynamic arguments "working" except that they don't actually work. Unlike the previous method that I used (evaluated when configure is executed), the arguments are only evaluated when autoconf is executed. This means (for example) that when I type 'make dist' the generated packag

Re: Automake 1.12.0b test release

2012-05-20 Thread Bob Friesenhahn
On Sun, 20 May 2012, Stefano Lattarini wrote: What is the workaround for this? Yes: the version-generating script should be executed at autoconf runtime instead; here is what GNU coreutils does, for example: AC_INIT([GNU coreutils], m4_esyscmd([build-aux/git-version-gen .tarball-v

Re: Automake 1.12.0b test release

2012-05-20 Thread Stefano Lattarini
[Re-adding the list, because I think the issue might be of general interest] On 05/20/2012 12:59 AM, Bob Friesenhahn wrote: > Stefano, > > This change will cause significant issues for GraphicsMagick unless there is > a workaround: > > - Support for the two- and three-arguments invocation form

Automake 1.12.0b test release

2012-05-19 Thread Stefano Lattarini
We are pleased to announce the Automake 1.12.0b test release. This release: - fixes few minor bugs, some weaknesses in the Automake's own testsuite and build system, and few inefficiencies in the implementation of the 'check' and 'recheck' targets (offered by