[Top][All Lists]

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

Re: libtool macros installed in pkgdatadir?

From: Scott James Remnant
Subject: Re: libtool macros installed in pkgdatadir?
Date: Wed, 28 Jan 2004 22:39:18 +0000

On Wed, 2004-01-28 at 22:26, Albert Chin wrote:

> On Wed, Jan 28, 2004 at 10:13:21PM +0000, Scott James Remnant wrote:
> > One day a version of Autoconf will use these, but for now when you run
> > aclocal it'll add an "m4_include" line to aclocal.m4 for each of these
> > files (rather than including them verbatim).
> Ugh. So *every* package providing useful 3rd-party autoconf macros
> must be copied locally to the package using them?
This is exactly what happens now, aclocal does exactly this.  Every
third party macro set gets copied locally into the package using it,
just into one great big unmanangeable file called aclocal.m4.

By giving this kind of thing to individual packages to maintain and
worry about, for example through autopoint and libtoolize (which both do
this now) -- better tracking is provided, you know that the m4 macros
you're relying on *haven't changed*.

Which will of course mean that every time random package changes its
macros, it *WON'T* break your configure script :-)

Having a directory of individual files rather than lumping them together
in aclocal.m4 is more manageable.

It's not really that big a change result-wise, it's just a much cleaner
way of doing things.

Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

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