Re: Best Practice for cvs2svn

James Levinson wrote:
> I am doing a cvs2svn conversion and I was hoping NOT to shutoff cvs, but
> let people migrate at their own pace...
>
> Thus, I have been trying to write a cvs hook script that would commit to
> svn. My logic was this: Commit to cvs Repos ---> Update cvs Working dir
> ---> Copy file to svn Working Dir ---> Commit to svn Repos.
>
> I was trying to do this all in a perl script called from the cvs loginfo
> hook. The problem is locking when I fire off the cvs update and I can't
> seem to get around it. I tried forking it into the background but no luck.
>
> Anybody ever try to do this ? Should I abandon and just do a big-bang
> migration of my dev team. Or is there another way? Any advice much
> appreciated ? Thanks.

I find there's always complications for cvs2svn conversions. Sometimes the CVS
author is blank, and you need an svn author since svn doesn't like blank
authors. So I recommend getting shell scripts written that handle each
conversion. Then put it in an svn repository for the developers to review.

If there are any issues, then just drop the Subversion repositories and rerun
the script with any tweaks.

Finally, when everybody is happy with it, then do a hard cut over.

You don't want to have both repositories up at the same time.

If you can do individual projects one at a time, then that's easier. You don't
have to cut the entire CVS repository over at once.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org