[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Cvs2svn - one repo/module

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-02-04 11:14:01 CET

Arnout Standaert <arnout.standaert@cit.kuleuven.ac.be> writes:

> Hi all,
> I have a small (newbie) question.
> I currently work on some small projects under Subversion, and I like
> what I see. I'm planning to migrate my larger projects from CVS to
> Subversion as soon as it hits 1.0 (or sooner, I think I can't wait).
> So, cvs2svn.py would be the way to go. But: all my projects are now in
> one big CVS repository as separate modules. I would like to split them
> up into several SVN repositories, as most of them are quite
> independent of each other.
> Is there a way to tell cvs2svn to convert the CVS modules in one CVS
> repository to separate SVN repositories?

Yeah, just convert the subdirs that represent your modules. I mean,
on Unix, you could do something like (typing without trying this, so
pay attention only to the gist of my idea):

   $ cd /path/to/cvs/repos
   $ for module in `ls -1 | grep -v CVSROOT`; do \
        cvs2svn.py --create -s ${module}-svn-repos ${module}; done

> Or is there a way to split the one big SVN repository afterwards
> into separate repositories, while preserving version history?

Kinda. But the problem you'll run into here is that all your tags and
branches from various modules will be intertwined in the /tags and
/branches directory, and trying to use something like svndumpfilter to
sort that mess out just ain't worth it. Try the method above first.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 4 11:15:20 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.