From: Christopher Morrison <brlcad@ma...> - 2008-01-11 20:16:31
The migration of the BRL-CAD repository from CVS to Subersion is now pretty much complete or at least really close to being complete, with just a few validation steps remaining. There were a handful of issues encountered including some cleanup of the CVS repository that was needed, but in all it's been a pretty painless conversion. For details on the conversion process, I've documented everything up on the new wiki here: http://my.brlcad.org/wiki/Cvs2svn
As some will notice if you haven't already, commit access to the CVS repository was shut off with an access control list. This was done when the conversion began (about a week ago) so that I didn't have to manually migrate patches that could have occurred from the time conversion was started until now. That isn't to say, however, that you'll have to redo any pending CVS changes you had going -- you can migrate your changes to an SVN checkout pretty easily.
If you have changes in a CVS checkout that you'd like to migrate, you can create a patch file from the checkout and then apply that patchfile to an SVN checkout:
# go to your cvs checkout dir
# create a patchfile of your changes
cvs diff -u > mychanges.patch
# go to your svn checkout dir
# apply the changes
patch -p0 < mychanges.patch
# commit when you're ready
For those not familiar with SVN, I think you'll (hopefully) be pleasantly surprised to find that almost every CVS command is available and works nearly the same with SVN. The command syntax is even identical for many/most commands where you just replace 'cvs' with 'svn' and it does what you'd expect. (e.g. svn commit instead of cvs commit, svn update instead of cvs update, etc) The one command that is somewhat different is how you specify the repository for checkout, as SVN uses URLs instead of the -d option and you don't need the -dP flags. This will get you the latest sources:
svn checkout https://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk brlcad
There's no login step or difference with anonymous checkouts either. It'll prompt you for a username/password the first time you try to commit, or you can specify the --username option during commit.
I'll send a separate e-mail out to the users mailing list when everything has been more fully validated and verified with more basic usage details. For now, I'm still waiting on the results of our Ohloh enlistment to complete so stats can be compared as a final sanity check.
If you see anything wrong or unexpected in the repository, now would be the time to speak up and point it out. Otherwise, it looks like we should now be good to go.