Date: Mon, 27 Apr 2009 19:39:53 +0300 From: Giorgos Keramidas <keramida@freebsd.org> To: John Nielsen <lists@jnielsen.net> Cc: freebsd-questions@freebsd.org Subject: Re: CVS history access? Message-ID: <87ws963vae.fsf@kobe.laptop> In-Reply-To: <200904271123.32647.lists@jnielsen.net> (John Nielsen's message of "Mon, 27 Apr 2009 11:23:32 -0400") References: <200904240535.37460.lists@jnielsen.net> <874owc8bfx.fsf@kobe.laptop> <200904271123.32647.lists@jnielsen.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
There are online instructions for mirroring a full CVS copy, so it
should be relatively easy to do that. It mostly boils down to setting
up the necessary disk space somewhere locally, installing one of the
CVSup ports and configuring a `supfile' like this:
*default host=CHANGE_THIS.freebsd.org
*default base=/path/to/local/cvs/mirror
*default prefix=/path/to/local/cvs/mirror
*default release=cvs
*default delete use-rel-suffix
*default compress
cvs-all
Yo should change `CHANGE_THIS' with the hostname of a CVSup mirror (a
full list can be found in the Handbook), and then point the local CVS
mirror directory from `/path/to/local/cvs/mirror' to the place you will
keep the mirror.
To pull over the CVS mirror files, you can then run:
# cvsup -g -L 2 supfile
Note that this will take quite some time if you are starting from an
empty mirror, and it may be a good idea to rerun cvsup 1-2 times after
it's done, to make sure you have the latest changes -- including any
changes that were committed between the time you started mirroring and
the time the first run was done.
FYI, my local copy of the repository uses around 4 GB today, so you
should plan to keep the mirror on a disk with at least this amount of
space (a few extra GB won't hurt either):
# du -sh /home/ncvs
4.0G /home/ncvs
#
>> We also have a Subversion repository now, that you can use to grab
>> commit information. It takes slightly more disk space than the CVS
>> repository, but subversion can export XML formatted commit logs, which
>> may be slightly more useful if you plan to automate parts of the
>> parsing and info-gathering.
>
> Yes, I'll definitely be automating the parsing, etc. Is it safe to
> assume that the cvs2svn migration went successfully? XML logs do sound
> appealing and aggregated (same time, multiple files) commits would be
> more useful than per-file. Can I just check everything out from
> svn://svn.freebsd.org/base/?
The conversion from CVS to Subversion was ``good enough'' from what I
see in the svn commit logs. So it may be a good idea to use `svnsync'
to mirror the /base/ repository locally and take it from there.
The instructions for mirroring the Subversion repository are a bit more
involved, but if you decide to go that way, let me know and I will write
a short description of how to do it.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iEYEARECAAYFAkn13+MACgkQ1g+UGjGGA7YljACgwbckVjHEKedW/jRpDK8OWg3J
sFQAn1NdegE/fX8Zp9yvenhdm2BI7uzM
=ExoD
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87ws963vae.fsf>