I want to convert a large, multi-module CVS repository to svn using
one svn repos per module. I have done it once and have been pleased
with the results. I did have a couple of CVS issues I was able to
resolve with some fiddling inside CVS, but my modules were simple,
i.e., they checked out with no cross-module connection.
However, the CVS repos I want to convert now does have intertwined
modules. Example, we have top-level modules A, B, C, D, E. In the
CVSROOT modules file we have:
A A &C &D
B B &E
I want the svn repos to look like:
A/C
A/D
B/E
where A and B are separate svn repos and C, D, and E are just ordinary
dependent directories under their parents.
In other words, I want C, D, and E to no longer be independent
modules. The question is, is it best to (1) make the change manually
inside the CVS repos, or (2) to do it under svn later. I want to
preserve history so my naive view is the I can manually change a few
things around in the CVS repo (carefully, and on a copy of course), so
option 1 is the better route.
What will cvs2svn do with the module cross-reference if I take option 2?
To the best of my knowledge, modules C, D, and E have never been
independently worked on outside the checkout of A or B. But to
complicate the matter, there was a single branch taken on A long ago
which has become the de facto main line of development with no sign of
ever being merged back to the HEAD. After a successful conversion to
svn, I plan to copy A's trunk to a new branch, and then copy the
original branch to the trunk, thereby making it the main line of
development
Advice welcome.
Thanks.
-Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-22 20:05:52 CEST