Re: Site Macro Directory

[Mark D. Roth]

On Mon Jul 29 14:06 2002 +0200, Akim Demaille wrote:
> Thanks, I appreciate this.  Please, install.

Done.


> Nevertheless, I have talked again with my GNU Build System colleagues,
> and it seems there is something wrong going on.  You goal is to be
> able to install additional macros, right?  But the GCS aims at making

My goal is to be able to distribute my macros as independent packages,
not just to install and use them myself.  They're still available to
people, but it's easier to manage them if I can do it in one place
instead of in each package I distribute.


> self-contained packages.  So, while it is definitely right to install
> m4 files for someone like aclocal or autoreconf to copy them in the
> *local* directory, it is wrong to just use them.

That depends on what the GCS means by "self-contained packages".  The
package does include everything it needs to run the configure script
and build the code.  The only difference is that you need an external
macro package to regenerate the configure script.  However, you
already need an external package to regenerate the configure script,
because you need to have Autoconf itself!  So I really don't see what
the problem is here.


> I'm sorry for relaunching this issue, and I wonder how I could have
> left this going on.

I have to admit, this is quite frustrating.  I feel like we've had
this discussion at least three times now...

-- 
Mark D. Roth <address@hidden>
http://www.feep.net/~roth/