[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Updating a package's gnulib files in CVS
From: |
James Youngman |
Subject: |
Re: Updating a package's gnulib files in CVS |
Date: |
Mon, 26 Nov 2007 10:55:37 +0000 |
On Nov 26, 2007 7:48 AM, Simon Josefsson <address@hidden> wrote:
> That is what I do in my projects too: I commit gnulib files, but not
> other "generated" files. The problem I have with switching to any other
> mode is reproducibility. When checking out an old version of my
> software, how can I be sure to get the appropriate gnulib files? How do
> others that use the bootstrap tool solve this problem?
For findutils, I don't use the bootstrap tool. Instead I use a
hand-crufted script in findutils. Findutils has a config file that
contains a gnulib version identifier and a list of modules.
Essentially it checks gnulib out using "cvs checkout -D" to get a
reproducible version and then imports the indicated modules. The
config file and the script which reads it are checked into CVS and
included in findutils releases.
James.