[Top][All Lists]

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

Re: 10-gary-rewrite-libtoolize.patch

From: Gary V. Vaughan
Subject: Re: 10-gary-rewrite-libtoolize.patch
Date: Fri, 03 Oct 2003 14:22:45 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925 Thunderbird/0.3

Alexandre Duret-Lutz wrote:
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.

This convinced me.

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'.

Agreed.  It's a pity though, because without `autoconf --trace', we have
to go back to grepping (and a possibly missing or out of date
aclocal.m4) for use of AC_PROG_LIBTOOL and AC_LIB_LTDL, and to check for
installation directories declared with AC_CONFIG_AUX_DIR and AC_CONFIG_M4_DIR (when that macro arrives), which is much more brittle than tracing :-(


  ())_.  Gary V. Vaughan    gary@(|
  ( '/   Research Scientist       ,_())____
  / )=   GNU Hacker  \'      `&
`(_~)_   Tech' Author   =`---d__/

reply via email to

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