Re: [PATCH 368] New libtoolize --no-warn option.

[Bob Friesenhahn]

On Tue, 29 Apr 2008, Gary V. Vaughan wrote:
> I hope this will allay Ralf's concerns for users who want to stick
> with deprecated macro interfaces, and don't want libtoolize to nag
> them to upgrade.
>
> Okay to commit?

The immediate concern I have with this approach (--no-warn) is that 
the main reason for using it is to make use of a package's 
"autogen.sh" (or whatever) more pleasing.  However, since old 
libtoolize does not support the option, it is likely to simply quit. 
As a result, --no-warn can not safely be used if it is possible that 
some developers are using old libtoolize while others are using modern 
libtoolize.  That makes it almost worthless.

This is one rare case where providing the option via an evironment 
variable is safer.  Then the many "autogen.sh" can set an environment 
variable to hush the warnings.  Did you consider that?

Bob
======================================
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/