Eric Blake wrote:
> Would it be worth grepping configure.ac, and if you detect AC_PREREQ([2.60]),
> having that imply --assume-autoconf=2.60?
Implemented:
2006-07-29 Bruno Haible <[EMAIL PROTECTED]>
* gnulib-tool (SORT): New variable.
(func_usage): Undocument --assume-autoconf
Eric Blake wrote:
> Would it be worth grepping configure.ac, and if you detect AC_PREREQ([2.60]),
> having that imply --assume-autoconf=2.60?
Yes, excellent idea. There is no need to store the minimum autoconf
version in two different places, in configure.ac and gnulib-cache.m4.
Bruno
Bruno Haible <[EMAIL PROTECTED]> writes:
> I added a --assume-autoconf command line options. You can use
> --assume-autoconf=2.60; 2.59 is the default for now.
Thanks, this is nicer. (Should I set my alarm clock to increment the
default in July 2007? :-)
I'd rather not put '--assume-autoconf=
Bruno Haible clisp.org> writes:
>
> Paul Eggert wrote on 2006-07-09:
> > While bootstrapping Bison I noticed that gnulib-tool assumes Autoconf
> > versions 2.57 through 2.59. But Bison assumes 2.60. On the theory
> > that gnulib-tool should assume the latest stable version, and you
> > can cop
Paul Eggert wrote on 2006-07-09:
> While bootstrapping Bison I noticed that gnulib-tool assumes Autoconf
> versions 2.57 through 2.59. But Bison assumes 2.60. On the theory
> that gnulib-tool should assume the latest stable version, and you
> can copy onceonly by hand if you want an earlier one
* Paul Eggert wrote on Sun, Jul 09, 2006 at 05:33:47AM CEST:
>
> * gnulib-tool (func_get_filelist): Don't echo m4/onceonly_2_57.m4,
> for the benefit of people using Autoconf 2.60. If you want to
> support older Autoconf versions you can copy m4/onceonly_2_57.m4
> (or m4/o
While bootstrapping Bison I noticed that gnulib-tool assumes Autoconf
versions 2.57 through 2.59. But Bison assumes 2.60. On the theory
that gnulib-tool should assume the latest stable version, and you
can copy onceonly by hand if you want an earlier one, I installed
this:
2006-07-08 Paul Egger
