[Top][All Lists]

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

Re: 10-gary-rewrite-libtoolize.patch

From: Alexandre Duret-Lutz
Subject: Re: 10-gary-rewrite-libtoolize.patch
Date: Fri, 3 Oct 2003 14:12:34 +0200

On Fri, Oct 03, 2003 at 12:43:57PM +0100, Gary V. Vaughan wrote:
> Akim Demaille wrote:
> >I'm not sure libtoolize should run aclocal.  If it does, then with
> >autoreconf, aclocal is run many times :(
> Autoreconf can set ACLOCAL=: in libtoolize's environment if it knows that
> aclocal.m4 is already up to date.  The new libtoolize also runs autopoint,
> but only if --install is passed.
> I think it is important for libtoolize to `just work', and now that it runs
> `autoconf --trace' aclocal.m4 has to be up to date. :-(

Looks like this patch opened a can of worms.

What happens if Bruno wants to run `autoconf --trace' in
gettextize/autopoint for the same reason as you in libtoolize.  Should
these tools call libtoolize and aclocal too?  That can't work.

What if we introduce another tool that must run before aclocal?  In
the current (centralized) setup only autoreconf has to be updated.
With your patch, both autoreconf and libtoolize has to be updated.  If
more tools copy libtoolize, all of them will have to be updated.

I believe that tools which build/install aclocal.m4's sources should
not be allowed to run `aclocal', let alone `autoconf --trace'.

reply via email to

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