On Jan 11, 2008 4:19 PM, Ryan Schmidt <subversion-2007b_at_ryandesign.com> wrote:
> On Jan 11, 2008, at 16:34, Peter Wemm wrote:
> > 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)
> > Any suggestions or pointers would be greatly appreciated. Even "don't
> > use tool XXX" tips!
> I would suggest: don't do this at all. Use cvs2svn to convert your
> existing CVS repository to a Subversion repository. Then use the
> Subversion repository only. cvs2svn is a well-tested and often-used
> script so I hope it will work for you. If you have questions about
> cvs2svn, it has its own mailing list.
I'm very familiar with cvs2svn and talk with the developers regularly.
Our repository broke cvs2svn badly.
Besides, I think you missed the point. We can't kill the cvs tree as
it is a key part of our distribution infrastructure. I wasn't talking
about having parallel development going on in both cvs and svn.
cvs2svn would convert everything over on a one-time basis, then all
development would happen exclusively in svn. A bot would export the
changes to the legacy cvs tree, just like we do with our perforce
We can't just kill access via anoncvs, cvsup and CTM because it is convenient.
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-12 01:54:53 CET