GNU Automake 1.12.3 released

We are pleased to announce the Automake 1.12.3 maintenance release. This release: - reworks and reshuffles the Automake testsuite a bit; fixing some weaknesses and spurious failures in the process, but also, likely, introducing new ones; - introduces initial support for automatic dep

v1.11.6 tag missing from automake.git?

I see v1.12.2, but no tag for v1.11.6 for the CVE-2012-3386 fix. Is this intentional? -- Eric Blake ebl...@redhat.com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature

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

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: v1.11.6 tag missing from automake.git?

Hi Eric. On 08/15/2012 12:16 AM, Eric Blake wrote: > I see v1.12.2, but no tag for v1.11.6 for the CVE-2012-3386 fix. > Hmm... I can see it without problems: User error on your part, or am I missing something? Regards, Stefano

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

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: v1.11.6 tag missing from automake.git?

On 08/14/2012 04:24 PM, Stefano Lattarini wrote: > Hi Eric. > > On 08/15/2012 12:16 AM, Eric Blake wrote: >> I see v1.12.2, but no tag for v1.11.6 for the CVE-2012-3386 fix. >> > Hmm... I can see it without problems: > > > > User

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

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

Stefano Lattarini 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 unavailable for source trees no