libtool macros must be installed where aclocal can find them

[Per Bothner]

Having libtool copy all of its macros into a "project
macro directory" seems a silly idea.  What's the point?
As a developer, I have libtool installed, and might as well
use the installed m4 files.  When I make a release, I don't
need to m4 files either, because aclocal has copied them to aclocal.m4.
Having libtoolize copy m4 files to AC_CONFIG_MACRO_DIR is the
Wrong Thing to do.  Perhaps I'm missing something here.

The solution is that aclocal or libtool must be fixed so that aclocal
automtically searches the libtool m4 installation directory
$datadir/libtool-$version/m4.

There are of course a number of solutions:
* modify aclocal so it searched the libtool install directory.
* having libtool install its files in one of the default aclocal directories.

One relatively clean & simple solution, which doesn't require modifying aclocal:
* Add $datadir/libtool-$version/m4 to $datadir/aclocal/dirlist, which aclocal
reads to get a list of directories
to search. (You'd probably want to remove any old libtool lines from dirlist.)
--
        --Per Bothner
address@hidden   http://per.bothner.com/