Simon Josefsson <[EMAIL PROTECTED]> writes: > Eric Blake <[EMAIL PROTECTED]> writes: > >> According to Eric Blake on 3/20/2008 7:20 AM: >> | Here's stage 1 for the gnulib side - picking up useful tricks from >> | coreutils into gnulib's copy. I'd still like to consider splitting the >> | module, and implementing gnulib-tool hooks to recognize top/GNUmakefile in >> | a module description as a request to install the file in '.', regardless >> | of whether build-aux is '.' or a subdirectory. >> >> What do you think of applying this as stage 2? > > On second thought, can't we make git-version-gen optional? Not everyone > uses git. I still have some projects that use GNUmakefile but use CVS.
In case I wasn't clear: I meant that git-version-gen should go into its own gnulib module. Projects that want it can import that module, and GNUmakefile would detect that it is present and use it. Projects that don't use git doesn't need to import that module, and the GNUmakefile would notice that the file isn't available, and won't do anything about git-versions. /Simon
