Issue with 'modules' file while migrating cvs2svn

Hi All,

I have my main CVS repository in /cvsroot where many modules are present.

But all these modules are pulled together to form a single project (PRJ1)
using '*modules*' file in CVS.

*Example:*
/cvsroot/mod1
/cvsroot/mod2
/cvsroot/mod3
/cvsroot/mod4
/cvsroot/mod5
/cvsroot/mod6
/cvsroot/mod7

In modules file, it is defined using ampersand modules as follows:

PRJ1    &mod1  &mod2
mod2   &mod3
mod3   &mod4
mod4   &mod5
mod5   &mod6  &mod7

So whenever I do *cvs co PRJ1*, everything would be checked-out for me.

For folks, who are not sure about '*modules*' file and *ampersand modules*,
pls refer :
http://www.cvsnt.org/manual/html/Administrative-files.html#Ampersand-modules

My problem is when I run *./cvs2svn* to create a *dump *file, I need to give
a single CVS repository location as input. If I have to give multiple
projects, then it requires to give different --trunk, --branches and --tags
folders whereas I want everything to be listed under single tree (PRJ1).

But I don't have in that format now. Because each modules have it's own
version details (,v files) in itself. Hence each of them itself considered
as individual project.

How to crack this. Any pointers would be very much appreciated.

Thanks in Advance.
Arun Prasath

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2657181

To unsubscribe from this discussion, e-mail: [[email protected]].