Re: [Bug-gnulib] making it easier to import from gnulib

[Karl Berry]

    Currently it is quite error-prone to use a module from gnulib. 

I agree ... not that this is surprising.  The whole idea of `module' is
beyond what Jim and I originally had in mind (I'm not sure about Jeff's
original idea), which was just a place to store common source files, not
exactly to increase portability or anything, just to reduce redundancy.

Be that as it may, I like your idea.

    modules/

I'm not clear on when a file goes into modules/ and when into lib/,
seems like <module>.am could go into modules.  I'd rather have the
source dirs as clean as possible.

For that matter, instead of having lots of little files, how about
having one file per module with all the necessary information about that
module?  Or even, since there really aren't that many modules, just put
all the information into MODULES.txt.

   * gnulibize.

So a maintainer has gnulib checked out from cvs and runs gnulibize from
there?  Sounds ok to me.  As long as gnulib doesn't have to get "installed".

    The idea is to create a testing directory for each module, 

Cool.

    What is the minimum version of autoconf that I should care about? Is
    2.57 OK for everyone?

It is with me.

Thanks,
karl