You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andrew Norman <An...@erudine.com> on 2006/12/20 14:38:16 UTC
Suggestions for CVS->SVN Migration
I have recently migrated a CVS repository to SVN. Now this was the first
pass at the solution and I am not sure that I am doing it the right way
or the suggested layout to make support/branching and working with the
system easier. So I have decided to ask the enlightened people on this
list for some wisdom.
Current Layout:
CVS (Around 60 Eclipse projects):
Project1
Project2
Project3
SVN (Migrated: Approach One)
Toolkit/trunk/base/Project1
Toolkit/branches/0-0-1/base/Project1
Toolkit/branches/0-0-2/base/Project1
Toolkit/trunk/extensions/Project2
Toolkit/branches/0-0-1/extensions/Project2
Toolkit/branches/0-0-2/extensions/Project2
Customer/trunk/Project3
Note:
1/ The Customer set of projects don't have any branches/tags at the
moment
2/ The Toolkit Projects are desired to be in two separate groups but the
commits/version numbers are the same due to the close coupling between
the projects.
3/ The major aim of the migration is the use of atomic commits across
the various projects as we have been having problems with partial CVS
commits across the projects colliding.
Now each of the projects in the SVN are checked out to appear the same
as the initial CVS projects when working in Eclipse. Currently we are
having problems merging and seem to lose files (I think half of this is
probably education of the developers using the subversive plug-in).
What I am looking at is a major refactor of the repository to make the
conversion into Subversion easier to maintain in the long run. Because
currently I am feeling like the current solution is not going to be able
to be maintained for a long time as projects come and go during the
course of normal development.
Thanks
-Andrew
Re: Suggestions for CVS->SVN Migration
Posted by Michael Haggerty <mh...@alum.mit.edu>.
Les Mikesell wrote:
> On Wed, 2006-12-20 at 14:38 +0000, Andrew Norman wrote:
>
>> Current Layout:
>>
>> CVS (Around 60 Eclipse projects):
>> Project1
>> Project2
>> Project3
>>
>> SVN (Migrated: Approach One)
>>
>> Toolkit/trunk/base/Project1
>> Toolkit/branches/0-0-1/base/Project1
>> Toolkit/branches/0-0-2/base/Project1
>> Toolkit/trunk/extensions/Project2
>> Toolkit/branches/0-0-1/extensions/Project2
>> Toolkit/branches/0-0-2/extensions/Project2
>> Customer/trunk/Project3
>>
>> Note:
>> 1/ The Customer set of projects don't have any branches/tags at the
>> moment
>
> You probably want to cvs2svn the individual project modules separately
> so you get the branch/trunk/tags directories for each, then svnadmin
> load them with a -parent-dir argument to splice them where you want in
> the subversion repository.
As of version 1.5.0, cvs2svn supports multiproject conversions
(converting multiple subprojects, each with its own trunk/tags/branches
directories, within a single run of cvs2svn). This mode of operation is
preferred to running cvs2svn multiple times as it preserves the
chronological order of the commits across projects.
See the cvs2svn docs for details. Please note that you have to use the
--config file method of running cvs2svn to use the multiproject feature.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Suggestions for CVS->SVN Migration
Posted by Les Mikesell <le...@gmail.com>.
On Wed, 2006-12-20 at 14:38 +0000, Andrew Norman wrote:
> Current Layout:
>
> CVS (Around 60 Eclipse projects):
> Project1
> Project2
> Project3
>
> SVN (Migrated: Approach One)
>
> Toolkit/trunk/base/Project1
> Toolkit/branches/0-0-1/base/Project1
> Toolkit/branches/0-0-2/base/Project1
> Toolkit/trunk/extensions/Project2
> Toolkit/branches/0-0-1/extensions/Project2
> Toolkit/branches/0-0-2/extensions/Project2
> Customer/trunk/Project3
>
> Note:
> 1/ The Customer set of projects don't have any branches/tags at the
> moment
You probably want to cvs2svn the individual project modules separately
so you get the branch/trunk/tags directories for each, then svnadmin
load them with a -parent-dir argument to splice them where you want in
the subversion repository.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org