Re: autoconf 2.61 versus 2.68

[Guy Harris <guy () alum mit edu>]

On Apr 15, 2013, at 7:18 AM, François-Xavier Le Bail <fx.lebail () yahoo com> wrote:

> > From: Guy Harris <guy () alum mit edu>
> > If we want to ensure that the configuration scripts we ship are generated by a 
> > particular version of autoconf, we should remove configure from the repository, 
> > add an autogen.sh script to re-generate the configure file, and ensure that 
> > it's run as part of the release-tarball building process.
>
> Similar way:
> - remove configure and config.h.in from repository,
> - change AC_PREREQ Macro in configure.in, for example : AC_PREREQ(2.68),
> - run "autoreconf"as part of the release-tarball building process.

The only difference there is the AC_PREREQ() macro and hardwiring "autoreconf" as the "remake the configure script" 
process.

The latter is probably OK if we're not going to use automake.

The former requires developers who work from Git to have that autoconf 2.68 or later.  I'm not sure we need to require 
2.68, even if it happens to be the version on the machine that builds the release tarballs.  AC_PREREQ() should specify 
the minimum number known to build the current version of configure.in (so that somebody who doesn't have that version 
gets a "sorry, you need autoconf X.YY or later" error rather than some weird error).

_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers