Re: [PATCH] Make inter-release --version output more useful.

[Jim Meyering]

Ralf Wildenhues <address@hidden> wrote:

> * Jim Meyering wrote on Sat, Oct 27, 2007 at 09:09:21PM CEST:
>> Ralf Wildenhues <address@hidden> wrote:
>> > * Jim Meyering wrote on Sat, Oct 27, 2007 at 07:38:23PM CEST:
>> > [...git-version-gen...]
>> >> +        COREUTILS-[0-9]*) v=`echo "$v" | sed 's/^COREUTILS-//;s/_/./g'` 
>> >> ;;
>> >
>> > Does that need adjustment for Autoconf?
>>
>> No, since autoconf's preceding tag is of the right form.
>>
>> It's harmless, and I preferred to keep the scripts in sync.

Actually, I've made another change (to add these lines):

  # Don't declare a version "dirty" merely because a time stamp has changed.
  git-status > /dev/null 2>&1

so have lost sync.  So I've gone ahead and removed
the COREUTILS-specific one after all.

>> So, what do you think about removing them and suggesting automake -a
>> in README-hacking?
>
> Sure.  Actually, I would suggest, in case a build tree is already
> around,
>   ( PATH=$build/tests:$PATH; autoreconf -vi )
>
> (the subshell so $PATH is not permanently damaged, and the semicolon, so
> autoreconf is taken from the current tree, too, if present),
> or for simplicity, since users are likely to build in-tree anyway,
>   ( PATH=`pwd`/tests:$PATH; autoreconf -vi )

The rules in GNUmakefile are only ever used in a srcdir build,
so I'm using this now:

      dummy := $(shell rm -rf autom4te.cache; PATH=`pwd`/tests:$$PATH; 
autoreconf -i)

and putting this in README-hacking:

    The next step is to generate files like configure and Makefile.in:

            $ cd autoconf
            $ ( PATH=`pwd`/tests:$PATH; autoreconf -vi )