Re: Best Practice for CVS user who is converting to SVN - Ideas

FC2 with svn 1.0.8

So I tried 3 ways to convert cvs repo to a svn repo, this is what I found:

The facts
cvs repo - /var/repo/cvs/dev
svn repo - /var/repo/svn/dev

The methods
1. Treat cvs as a single repository and convert it to a single svn
repository with:

  cvs2svn -s <svn repo> <cvs repo>

2. Break up the cvs repositories and convert them into app repositories
in svn with:

  Modules="<list of modules>"
  for Module in $Modules; do
    cvs2svn -s <svn repo>/$Module <cvs repo>/$Module
  done

The second method was much more complicated than that but I wanted to
get just the understanding of it down not the specifics. Both methods
work just fine, but the second seems to keep my apps separated better so
that I can admin them in different ways. Cool. My scripts to do
method 2 were complicated but it did produce the end result that I think
I wanted. However....

One thing that I noticed is size of the root repository when I was done
with each (oh I did the 2 methods on separate systems). Here is what I
found:

initial cvs repo - 20 MB
method 1 svn repo - 25 MB
method 2 svn repo - 176 MB

This surprised me because I thought it would be close to the same. Not
close to 9 times greater than the size of the cvs repo. Did I do
something wrong or is this just the overhead that separate svn repos have?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 9 23:45:34 2004