Re: Updating CVS

[Mark D. Baushke]

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

Fouts Christopher (IFNA MP) <address@hidden> writes:

> When updating to a newer version, is the $CVSROOT/CVSROOT
> directory affected if I (do/don't do) a cvs init? I guess
> in general, when updating from an existing version (1.10.8)
> to a newer version (1.11.14), what needs to be done?

The 'cvs init' should only add files that are not already present but
are needed by cvs. I believe there are indeed a few such that have
arisen between 1.10.8 and 1.11.4, but I don't recall exactly. The 'cvs
init' function should not do anything bad to your files unless you
happen to have files in the $CVSROOT/CVSROOT that do not match the
top-of-tree version in their corresponding ,v file in the checkoutlist.

It is probably a good idea to create a test copy of the CVSROOT
directory into another repository and run the 'cvs init' command to see
what it does to your test setup before you do the real thing.

        Good luck,
        -- Mark

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFAmCrX3x41pRYZE/gRAg2lAKDFT19lKcBl6riv+4aIueqqOMvn2ACfScJA
+/cALMS+j9kSXacuyUZMV7I=
=EtFq
-----END PGP SIGNATURE-----