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

Can anybody point me to a *live* svn -> cvs exporter?

From: Peter Wemm <peter_at_wemm.org>
Date: Fri, 11 Jan 2008 14:34:49 -0800

I'm trying to organize a switch from a cvs repository to svn, but we
have the problem that we have a considerable infrastructure built
around cvs. Realistically, we can never be rid of it. So, besides
converting our 15 years of cvs history to svn, a prerequisite is to be
able to continuously export svn changes back to the cvs tree and make
it "look real".

We did something like this for using perforce. We have a process that
polls the p4 server for changes, then extracts them one at a time when
it finds them and commit them to the cvs tree. (We do this at work
too, where its been going happily for 7 years now. We still cut
releases from the replicated cvs tree, not perforce)

I've seen some other projects do this when switching from cvs to svn.
So far I haven't been able to find the people at those projects who
know how it was done.

If anybody has suggestions of where I could look, it would be
appreciated. I'm quite ready to write our own, but it would be silly
if there was a good solution "out there" that I haven't found yet.

Things I need: (either find a tool or modify one, or write my own)
export trunk to cvs HEAD.
export certain branches to certain cvs branches (a structured naming convention)
be able to deal with branches of branches in cvs.
If possible, somehow be able to magically deal with certain tags. (eg:
release tags)

The toughest one is the tags problem. We may just punt and do it by
hand for now - have the release engineers create both svn and cvs tags
at the same time. It would be nice if they didn't have to though.

We do *not* need to maintain the vendor branches in cvs.

I've found a bunch of one-time copy tools, or things that are so
heavy-weight that they're impractical. Or live p4->cvs converter is a
hundred lines of perl, for example - but it is admittedly a hack,
somewhat fragile, and only does trunk/head. I can hack that into
tracking svn if necessary, but I'm hoping I can find something

Any suggestions or pointers would be greatly appreciated. Even "don't
use tool XXX" tips!

Peter Wemm - peter_at_wemm.org; peter_at_FreeBSD.org; peter_at_yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-11 23:35:11 CET

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.