Re: Issue with 'modules' file while migrating cvs2svn

Hi All,

I am a newbie to both CVS and cvs2svn. So little worried about doing things
without proper knowledge.

Does anyone have any inputs on this. I need this info badly.  Can I do the
below to re-construct the repo manually under /cvsroot?

mkdir PRJ1
cd PRJ1
mkdir mod1 mod2 mod3 mod4
cd mod1
mv /cvsroot/subdir1.....subdir10    .
cd sbudir2
mv /cvsroot/sub-sub-dir1......sub-sub-dir6  .

regds,
Arun

On Sat, Sep 11, 2010 at 6:16 PM, Arun Prasath Vetriselvan <
[email protected]> wrote:

> Hi Max,
>
> Thanks for the reply. I gave just an example in this case and it is not the
> original structure with my project.
>
> Actually there are some folders which doesn't exist and it is just being
> formed on the fly with the help of modules file.
>
> Also there are many different sub directories actually put to form one
> module.
>
> That is, my modules file will be somewhat like this :
>
> PRJ1  &mod1  &mod2 &mod3 &mod4
>
> mod1  &subdir1  &sub2dir2..........&subdir10
>
> subdir2  &sub-sub-dir1  &sub-sub-dir2......&sub-sub-dir6
>
> mod2  &subdir1  &subdir2.....&subdir6
>
> mod3  &subdir1  &subdir2 .......&subdir5
>
> mod4 &subdir1.....&subdir4
>
> PRJ1 is being formed by combining 4 modules folders. But PRJ1, mod1 and
> subdir2 folders also doesn't exist actually in the /cvsroot path. Only the
> individual sub-directories are present. It goes in a similar
> fashion. Here sub-directories listed under each modules are different.
>
> Pls let me know if I can make a directory(PRJ1) as you mentioned and move
> the sub directories folders by creating corresponding modules folders inside
> the /cvsroot itself ?
>
> Will that allow me to create a proper SVN repo. with the same structure as
> I expect without any damage to the existing CVS repo ?
>
> regards
> Arun
>
>
> On 9/9/10, Max Bowsher <[email protected]> wrote:
>>
>> On 09/09/10 13:01, Arun Prasath Vetriselvan wrote:
>> > 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.
>>
>> "modules" is a CVS feature that doesn't map well into other version
>> control systems, and cvs2svn doesn't pay any attention to it.
>>
>> But, in this case it sounds like you could just rearrange your cvs
>> repository to make the modules file irrelevant:
>>
>> cd /cvsroot
>> mkdir PRJ1
>> mv mod6 mod7 mod5
>> mv mod5 mod4
>> mv mod4 mod3
>> mv mod3 mod2
>> mv mod1 mod2 PRJ1
>>
>>
>> Max.
>>
>>
>>
>

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

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