(Sorry about my tardiness in replying; also, moved bug-gnulib to BCC
and added bug-findutils)
On Nov 27, 2007 12:06 PM, Jim Meyering <[EMAIL PROTECTED]> wrote:
> I'm feel about CVS the way I've felt about K&R C for years now.
> It's worth supporting if doing so is really easy (i.e., "automatic"),
"James Youngman" <[EMAIL PROTECTED]> wrote:
> On Nov 26, 2007 10:55 AM, James Youngman <[EMAIL PROTECTED]> wrote:
>> 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 a
On Nov 26, 2007 10:55 AM, James Youngman <[EMAIL PROTECTED]> wrote:
> 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 r
gl_REVISION([abc6ba7cb8ac9acb9acd..])
I don't have any objection to such a feature, but I probably wouldn't
use it myself -- I update from gnulib too often to want to munge
configure.ac every time. Pretty much the only time I refrain from
updating is nearing a release.
Best,
karl
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Karl Berry) writes:
>
>> The three possibilities are listed in
>> http://www.gnu.org/software/gettext/manual/html_node/Files-under-CVS.html
>>
>> There's another possibility, which apparently both you and I follow in
>> differ
On Nov 26, 2007 7:48 AM, Simon Josefsson <[EMAIL PROTECTED]> 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 ca
[EMAIL PROTECTED] (Karl Berry) writes:
> The three possibilities are listed in
> http://www.gnu.org/software/gettext/manual/html_node/Files-under-CVS.html
>
> There's another possibility, which apparently both you and I follow in
> different ways: commit some (but not all) autogenerated fi
The three possibilities are listed in
http://www.gnu.org/software/gettext/manual/html_node/Files-under-CVS.html
There's another possibility, which apparently both you and I follow in
different ways: commit some (but not all) autogenerated files.
It doesn't have to be an all-or-nothing deci
Denver Gingerich wrote:
> > It also appears to install new files with an added "_" (ie. stdlib_.h).
You must be using a gnulib checkout that is already a month old or more?
We renamed all *_.h files to *.in.h recently.
Eric Blake wrote:
> Now for some background: there are two schools of thought
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Karl Berry on 11/18/2007 5:16 PM:
> Hi Denver,
>
> The .cvsignore behavior works right for me. The ignored files are
> precisely those which should be recreated by people running configure on
> their individual systems; they shouldn't b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Denver Gingerich on 11/18/2007 5:03 PM:
> I would like to update the gnulib files for the package I'm
> maintaining (wdiff) in CVS (I've decided to check-in the gnulib files
> so people using CVS don't have to run gnulib). However, runnin
Hi Denver,
The .cvsignore behavior works right for me. The ignored files are
precisely those which should be recreated by people running configure on
their individual systems; they shouldn't be checked in.
karl
I would like to update the gnulib files for the package I'm
maintaining (wdiff) in CVS (I've decided to check-in the gnulib files
so people using CVS don't have to run gnulib). However, running
"gnulib-tool --import" or "gnulib-tool --update" creates a bunch of
files I don't want, such as .cvsigno
13 matches
Mail list logo
