Re: Copying vs m4_including macro files

[Akim Demaille]

 >> The autoconf part of this feature is trivial (I can provide a patch if
 >> that's useful), but I suspect I'd need to be able to write perl to
 >> implement the aclocal end :-)

 > Fortunately, if we consider relative directories as local, we don't
 > need to look at AC_CONFIG_M4_DIR.  Adding this macro to Autoconf is
 > probably a good thing for the future, though.

At the origin I was considering that AC_CONFIG_M4_DIR was
automatically passed to m4 as a -I, so instead of
m4_include([config/init.m4]) etc. you'd have m4_include([init.m4]).