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.

The GNUmakefile code that uses the script should check if the file is
available locally before doing anything, I think.

> +2008-03-20  maintainer-makefile
> +                            GNUmakefile now looks for cfg.mk, rather than
> +                            maint-cfg.mk.  It also depends on 
> git-version-gen,
> +                            so you should use this version in your AC_INIT:
> +                            m4_esyscmd([build-aux/git-version-gen 
> .tarball-version])

Further, can't we automate that somehow?  gl_EARLY?

/Simon


Reply via email to