[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: 77-gary-diagnose-version-mismatch.patch

From: Gary V. Vaughan
Subject: Re: RFC: 77-gary-diagnose-version-mismatch.patch
Date: Mon, 02 Feb 2004 13:22:58 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

Hash: SHA1

Scott James Remnant wrote:
| On Mon, 2004-02-02 at 11:15, Gary V. Vaughan wrote:
|>Albert Chin wrote:
|>| On Fri, Jan 30, 2004 at 05:54:28PM +0000, Gary V. Vaughan wrote:
|>|>This patch kind of fell out of me wanting libtool to do
|>|>automake-like version mismatch checking at runtime, and
|>|>autoconf-like AC_PREREQ version-minima.
|>|>If you guys like this, I'll rewrite the docs, update the test
|>|>directories and resubmit.
|>| Does your LT_INIT_LIBTOOL() error out for invalid options?
|>No it doesn't.
|>I'll add code for that in the next submission.
| In the interests of forward compatibility, it probably shouldn't *error*
| out...
| If in 1.6.2 we add a new option, we necessarily want 1.6 to suddenly
| stop working because people have included the new one.
| We know that Autoconf doesn't error when unknown configure arguments are
| given, what does Automake do if you give AM_INIT_AUTOMAKE an unknown
| option?  (afaict it doesn't)

Regardless of what the other tools do, it would be good engineering to let
the user know that the new-whiz-bang option he added to his is
actually being ignored by the old libtool.m4 he is using...

In which case, erroring is still a good thing IMHO.  Maybe the user spelled
the option wrongly?  Or worse is relying on the feature behind the option
for his build process.  If Automake doesn't error on bogus options, then I
think it should :-/

- --
Gary V. Vaughan      ())_.  address@hidden,}
Research Scientist   ( '/
GNU Hacker           / )=
Technical Author   `(_~)_
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -


reply via email to

[Prev in Thread] Current Thread [Next in Thread]