[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: address@hidden: Re: [Savannah-hackers] address@hidden: Re: emacs/src
From: |
Thien-Thi Nguyen |
Subject: |
Re: address@hidden: Re: [Savannah-hackers] address@hidden: Re: emacs/src/regex.c]] |
Date: |
Fri, 26 Dec 2003 02:40:27 -0500 |
From: David Kastrup <address@hidden>
Date: 25 Dec 2003 23:55:13 +0100
Any way to do this without this presumption? Would
cvs -d :ext:address@hidden:/cvsroot/gnulib \
checkout gnulib/regex.{c,h}
do the trick in the script?
i don't know if cvs expands {c,h} properly but if separated into two
distinct commands i'm sure that would work:
gnulib_cvsroot=':ext:address@hidden:/cvsroot/gnulib'
cvs -d $gnulib_cvsroot checkout gnulib/regex.h
cvs -d $gnulib_cvsroot checkout gnulib/regex.c
for some, disk space savings is probably not as important as bandwidth
savings: 5872 KB for all of gnulib vs 212 KB for only regex.[ch].
And presuming that it does: will an update on the whole Emacs
directory update those two files via their symlinks, from their
respective repositories? Probably not, right?
correct (hence wrapping the "cvs update" operation w/ this script).
the limitation lies w/ cvs, which operates on a directory-oriented
basis, and does not handle multiple CVSROOT in one logical operation,
at least the last time i probed its failure modes in depth (~1999).
the recent change in deployment to use chroot is even more reason to
do things client-side, ugly as it may appear initially.
thi
Re: address@hidden: Re: [Savannah-hackers] address@hidden: Re: emacs/src/regex.c]], Eli Zaretskii, 2003/12/25