Re: backing up of cvs repositories

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David,

CARTER-HITCHIN, David, GBM <address@hidden> writes:

> > > > >   --exclude '#cvs.lock' \
> > > > >   --exclude '#cvs.history.lock' \
> > > > >   --exlcude '#cvs.val-tags.lock' \
> > > > >   --exlcude '#cvs.rfl*' \
> > > > >   --exlcude '#cvs.pfl*' \
> > > > >   --exlcude '#cvs.wfl*' \
> > > > >   --exlcude ',*,' \
> > > > >   --exclude 'CVS'
> 
> If using rsync, then --cvs-exclude does the magic above.

I believe you are mistaken for versions of rsync
up to and including rsync-2.6.8 (which I believe
is still the latest revision available from
http://rsync.samba.org/).

The --cvs-exclude plays the same games as the
.cvsignore file and is great if you are using
rsync to copy a checked-out tree. It fails
completely to handle the cvs locks associated with
an active repository.

Look closely at the exclude.c file at what the
get_cvs_excludes() does with the users global
'.cvsignore' file and the CVSIGNORE environment
variable.

In fact, depending on how the file patterns are
specified in $HOME/.cvsignore, it is possible that
using --cvs-exclude would cause one or more files
in the repository that should be copied to be
ignored.

It may be that your particular version of rsync
has local patches which do the right thing, but
if so, they have not been ported back to the
official versions of rsync.

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEfatZCg7APGsDnFERAnTKAJ9aFvMguq6TeADfFb3xkXgt6BPtCQCfWGx3
bd7Jh1W8KCgE0eATcRe56C8=
=V/KX
-----END PGP SIGNATURE-----