[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hello 2.1.91 pretest

From: Karl Berry
Subject: Re: hello 2.1.91 pretest
Date: Mon, 21 Aug 2006 18:36:59 -0500

Hi Mark,

Thanks for taking a look at this.

    Hmmm... It might be nice if there were some kind of a readme that talks
    about the non-default location of the m4 directory being in gnulib/m4

Ok, good, I will add something to README.dev about that.

    instead of m4 ... 

I changed from the default because it didn't make sense to me to use
m4/, which historically has been a grabbag of files from all over.  So
using it for gnulib (only) would implicitly encourage mixing of gnulib
files and non-gnulib files.  Seems cleaner to give gnulib its own,
completely separate, directory.  (In fact, I'd somewhat argue that the
default should not be m4/, but I suppose it's too late now.)

    really need needing an 'autoreconf --include=gnulib/m4' as I will get

I don't understand.  I admit that I don't use autoreconf (controversial,
I know), because in my experience it copies older files over newer ones.
That's more or less why autogen.sh exists.

    thing with a missing gnulib/m4/gnulib-cache.m4 file and it appears that

I see.  Didn't we just discuss the pros and cons of including
gnulib-cache.m4 in the distribution?  I admit I don't remember the
outcome, sorry, but it seems like it would help.  Otherwise anyone
wanting to run gnulib has to reproduce all the options, and isn't that
exactly what gnulib-cache.m4 is there to avoid?

Or is the idea that anyone wanting to use gnulib should use the CVS
files?  Seems like that's not necessarily the case ... (doesn't matter
for hello as such, but it could be useful with real packages).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]