Feature request

[Albert Chin]

When building software with installable .m4 files (libtool, pkgconfig,
gtk+, etc.), if each software program is installed to a separate
directory, aclocal must be used like so:
  $ aclocal -I [path to libtool .m4 files] \
  -I [path to pkgconfig .m4 files] ...

How about an environment variable that aclocal would query that does
the job of -I? pkgconfig uses the PKG_CONFIG_PATH variable giving
locations for pkg-config to query for .pc files. Doing something
similar with aclocal would make automating use of aclocal in build
scripts much easier.

-- 
albert chin (address@hidden)