>>>>> "drv" == Didier Verna <[EMAIL PROTECTED]> writes:
>> I'd like to stick to a single email address.
drv> I don't have really strong feelings about this, but I'd
drv> like to hear other opinions however. My main concern is that, as
drv> always, if you don't give people the means to do what they want
drv> to do (to a certain extent, obvisouly, and *this* is not going
drv> very far in that direction anyway), they'll end up hacking their
drv> script with explicit calls to Autoconf's internal routines. We
drv> all know that this is shooting ourselves in the foot with respect
drv> to backward compatibility maintenance.
I think people are concerned by more severe limitations in Autoconf.
That's where we really need to do something.
A key point in Autoconf is remaining simple, and this does imply
sometimes be somewhat limited. Problems start with choice.
Let's not forget `configure' is not an end, it's just a means.
>> In addition, the string we use is quite standardized.
drv> Sounds like a Gnits concern more than a GNU one to me ?
Well, maybe :) I'm just sticking to what the tools I use most often
do.
drv> Yes I did, but maybe in the middle of one of your
drv> bunches... wait... ah, I see:
drv> | (AC_ARG_WITH): Remove spurious newline.
drv> Damn! I liked this blank lines :-)
Did you???
Well, to be honest, I'd like to see those two pseudo option
documentation moved into a paragraph just as we do for the variables:
| Optional Packages:
| --with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
| --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
| --without-included-regex don't compile regex; this is the default on
| systems with version 2 of the GNU C library
| (use with caution on other system)
| --with-included-gettext use the GNU gettext library included here
| --with-catgets use catgets functions if available
|
| Some influential environment variables:
| CC C compiler command
| CFLAGS C compiler flags
| CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
| headers in a nonstandard directory <include dir>
| LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
| nonstandard directory <lib dir>
|
| Use these variables to override the choices made by `configure' or to help
| it to find libraries and programs with nonstandard names/locations.
It is more standard too. Something like:
| Optional Packages:
| --without-included-regex don't compile regex; this is the default on
| systems with version 2 of the GNU C library
| (use with caution on other system)
| --with-included-gettext use the GNU gettext library included here
| --with-catgets use catgets functions if available
|
|
| Use --with-PACKAGE to include the optional PACKAGE. Using
| --without-PACKAGE is the same as --with-PACKAGE=no.
