[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 13 Oct 2000 09:48:15 -0400 (EDT)
> I'd like to avoid avoiding renamings for it makes the syntax cleaner.
> | I can imagine many configure.in's using it e.g. to add -Wall to CFLAGS.
> This is *bad*. But I hear your call. Consider my patch comes with
> AU_ALIAS(ac_cv_prog_gcc, ac_c_cv_compiler_gnu)
> (plus the quotes, of course ;)
I don't think that everybody will run autoupdate on their configure.in.
There are several cases when complete switching is not feasible (think of
I realize how painful it is when your patch is rejected, but after some
consideration I'm feel even worse about such changes that I felt
If you can avoid renaming the variables (by any means) then it's Ok to
apply now. If you cannot or don't want to preserve the traditional names
please delay the patch for after 2.50.
Otherwise the incompatibility between 2.13 and 2.50 can reach the level
when people will refrain from using Autoconf-2.50. This is a minor change,
but many minor changes create big problems.
Don't forget that configure.in is often written not by the same person
that writes the code. Not everybody has time to straighten other people's
There is one case when I'm ready to reconsider my objections - if this
patch is required to make further changes needed for 2.50.