Re: [PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file

2013-01-28 Thread Eric Blake
On 01/27/2013 11:16 AM, Peter Rosin wrote: > In e.g. the Cygwin case, it is often *required* that packages get > re-bootstrapped for them to work correctly, especially if they have been > bootstrapped with old tools. I even think cygport (the tool used to > package most stuff for Cygwin) by default

SGI/IRIX support (was: Re: [PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file)

2013-01-28 Thread Stefano Lattarini
On 01/28/2013 12:36 AM, Peter Rosin wrote: > > [SNIP] > > [re SGI support] > >>> What do you gain by the zap? >>> >> Not shipping broken code, and not having to debug/fix it for the >> benefit of a vanishingly-small user base. > > I agree, the zap is ok. But the rationale in NEWS comes out > all

Re: [PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file

2013-01-27 Thread Peter Rosin
Hi Stefano, Since you don't seem impressed by my arguments for keeping the support for configure.in, I will just stop wasting time and drop this discussion. I can't help myself though, and find myself repeating my arguments one last time... - I don't want to convert the GGI project from CVS, I d

Re: [PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file

2013-01-27 Thread Stefano Lattarini
On 01/27/2013 07:16 PM, Peter Rosin wrote: > On 2013-01-27 18:09, Stefano Lattarini wrote: >> Hi Peter. >> >> On 01/27/2013 12:26 AM, Peter Rosin wrote: >>> On 2012-12-29 00:39, Stefano Lattarini wrote: The autoconf input should be named 'configure.ac' instead. The use of 'configure.in'

Re: [PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file

2013-01-27 Thread Peter Rosin
On 2013-01-27 18:09, Stefano Lattarini wrote: > Hi Peter. > > On 01/27/2013 12:26 AM, Peter Rosin wrote: >> On 2012-12-29 00:39, Stefano Lattarini wrote: >>> The autoconf input should be named 'configure.ac' instead. The use >>> of 'configure.in' has been deprecated in Autoconf since at least >>>

Re: [PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file

2013-01-27 Thread Stefano Lattarini
Hi Peter. On 01/27/2013 12:26 AM, Peter Rosin wrote: > On 2012-12-29 00:39, Stefano Lattarini wrote: >> The autoconf input should be named 'configure.ac' instead. The use >> of 'configure.in' has been deprecated in Autoconf since at least >> the 2.13 -> 2.50 transition, and future Autoconf versio

Re: [PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file

2013-01-26 Thread Peter Rosin
On 2012-12-29 00:39, Stefano Lattarini wrote: > The autoconf input should be named 'configure.ac' instead. The use > of 'configure.in' has been deprecated in Autoconf since at least > the 2.13 -> 2.50 transition, and future Autoconf versions (starting > with 2.70 probably) will start to warn about

[PATCH 1/5] Drop support for 'configure.in' as the Autoconf input file

2012-12-28 Thread Stefano Lattarini
The autoconf input should be named 'configure.ac' instead. The use of 'configure.in' has been deprecated in Autoconf since at least the 2.13 -> 2.50 transition, and future Autoconf versions (starting with 2.70 probably) will start to warn about it at runtime. Automake has been warning about it si