[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: empty TIMESTAMP, stamp-vcl
From: |
James Youngman |
Subject: |
Re: empty TIMESTAMP, stamp-vcl |
Date: |
Wed, 28 Mar 2007 18:50:12 +0100 |
On 3/28/07, Gary V. Vaughan <address@hidden> wrote:
ii) except that doesn't tell us which gnulib release was used, so we
need to factor the gnulib timestamp information too :-( I think
we can maybe get away with just making bootstrap write a gnulib
repo timestamp into a version.c file...
Findutils deals with this by invoking gnulib-tool from a shell script,
import-gnulib.sh. import-gnuli.sh reads a file import-gnulib.config
which contains the version label for the required gnulib version. The
config file is included in the source distribution too, and recent
versions of findutils include the gnulib version in the result of
"find --version". Before import-gnulib.sh runs gnulib-tool, it
updates the sources from CVS (passing -D xxxx to get the right
version).
This is a bit cumbersome but I prefer it to the two obvious alternatives:
1. Copyng gnulib files into findutlils CVS
2. Applying findnutils version number tags to the gnulib sources (I
have no commit access to gnulib anyway).
See for example
http://cvs.savannah.gnu.org/viewcvs/findutils/import-gnulib.sh?rev=1.32&root=findutils&only_with_tag=HEAD&view=markup