automake-patches
[Top][All Lists]
Advanced

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

Re: am_init_automake-vs-ac_init.patch


From: Alexandre Duret-Lutz
Subject: Re: am_init_automake-vs-ac_init.patch
Date: 07 Jan 2002 00:51:55 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

>>> "Tom" == Tom Tromey <address@hidden> writes:

[...]

 Tom> What if we require a specific piece of text for the single-argument
 Tom> form?  I've occasionally regretted allowing any text as the 3rd
 Tom> argument.  One idea that used to get kicked around was having the 3rd
 Tom> argument be like the new AM_AUTOMAKE_OPTIONS -- but we couldn't do
 Tom> that for compatibility reasons.  Maybe we could rectify this error
 Tom> now.

I like this idea.  So I will rework the patch that way:

  - if there are three arguments, the third argument means that 
    PACKAGE and VERSION should not be defined, as in the past.
  - if there is one argument, this argument is taken to be a 
    space-separated list of Automake options: some of them
    (`no-define') are meaningful to AM_INIT_AUTOMAKE, the others
    are ignored by AM_INIT_AUTOMAKE but interpreted as global
    options by Automake.
  - AM_AUTOMAKE_OPTIONS support can be removed.

This doesn't allow to specify global Automake options if one
uses the old-style AM_INIT_AUTOMAKE call, but I can't see a case
where one would want to do that.
-- 
Alexandre Duret-Lutz



reply via email to

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