You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by James Levinson <jl...@ziprealty.com> on 2006/03/29 22:35:54 UTC
Best Practice for cvs2svn
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.
Re: Best Practice for cvs2svn
Posted by kfogel <kf...@collab.net>.
Can this thread happen on users@cvs2svn.tigris.org, not
users@subversion.tigris.org? Thanks.
-Karl
"James Levinson" <jl...@ziprealty.com> writes:
> 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.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Best Practice for cvs2svn
Posted by Blair Zajac <bl...@orcaware.com>.
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
<bl...@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
RE: Best Practice for cvs2svn
Posted by Res Pons <po...@hotmail.com>.
It's really better if you declare a freeze time on a weekend for developers
to stop using cvs then tarball it, follow the cvs2svn instruction and have
your uses to login to the new svn box on Monday. Otherwise, if they
continue checking in code into cvs, you'll have a chicken & egg syndrome on
your hands.
----Original Message Follows----
From: "James Levinson" <jl...@ziprealty.com>
To: <us...@subversion.tigris.org>
Subject: Best Practice for cvs2svn
Date: Wed, 29 Mar 2006 14:35:54 -0800
MIME-Version: 1.0
Received: from tigris.org ([64.125.133.100]) by bay0-mc2-f1.bay0.hotmail.com
with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Mar 2006 14:37:23 -0800
Received: (qmail 14761 invoked by uid 5000); 29 Mar 2006 22:37:17 -0000
Received: (qmail 14752 invoked from network); 29 Mar 2006 22:37:17 -0000
X-Message-Info: 6sSXyD95QpVP0XNskqgmkv2R3OKm8CDjw3j8xLksomY=
Mailing-List: contact users-help@subversion.tigris.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
list-help: <ma...@subversion.tigris.org>
list-unsubscribe: <ma...@subversion.tigris.org>
list-post: <ma...@subversion.tigris.org>
Delivered-To: mailing list users@subversion.tigris.org
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Best Practice for cvs2svn
Thread-Index: AcZTgSPeA0tz9BLBRDGsJLxz2pb5+Q==
Return-Path: users-return-47211-pons32=hotmail.com@subversion.tigris.org
X-OriginalArrivalTime: 29 Mar 2006 22:37:23.0362 (UTC)
FILETIME=[58E05020:01C65381]
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.
_________________________________________________________________
Don�t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org