Es schrieb Paul Eggert: > > > From: "Mark D. Roth" <[EMAIL PROTECTED]> > > Date: Thu, 16 May 2002 12:28:27 -0500 > > > > That's fine, as long as it gets invoked automatically when you invoke > > autoconf. It should all get done in one step. > > Personally, I dislike site directories since > they make it a hassle to move my stuff from one site to another. > However, I wouldn't object to having a configure-time option for > building autoconf, for people who like to have site directories. > > Unfortunately, I've seen so many proposals in this area that I'm a bit > lost as to what's being proposed. For example, I don't understand > where the stuff will get cached. I believe you mentioned that it will > get cached into aclocal.m4, but won't that collide with Automake's > aclocal?
yes it would. I did that quite a time with my tools to let aclocal read a directory of mine holding autoconf scripts which I did later convert to bind itself to the ac-archive. It did work most of the time, but note that "most", it wasn't quite good an idea to have that automated somehow. After deriving "acinclude" from the code of "aclocal", I don't quite know how I could live without it before - whenever an outer-macro changes, I can call "acinclude" and create a local `cache file` acinclude.m4 that automake's aclocal will see and use. By default, it also searches subdirectories of the current-one since that has proven to be veeeeery convenient... and useful. I do usually put this acinclude.m4 into cvs of the projects, so that co-workers don't need to install it on every platform, which did prove to be a good idea - only the guys who know how to program m4/autoconf will need the tool to update the acinclude.m4 file with the changes they made. In general, this is one or two persons even in BIG projects. > > > It would also be nice if the autoconf installation let you override > > the path of the site macro directory, > > I think that's essential. > > Also, I would say that for now there should not be a site macro > directory unless the autoconf installer or autoconf user says so. If > the feature proves to be popular, we can always change this default. no changing default - a new tool! ;-) ----------> http://ac-archive.sf.net
