RE: Question on Migrating CVS Projects to SVN Single Repository

Hi Michael,

Thanks for your response.  I was able to figure out the solution after asking the question thru forum. 

I tried to create the repository and migrate using --existing-svnrepos option, but I continue to fail because I didn't setup other options such as "--fs-type", "--bdb-txn-nosync", and "--create-option".  So I just create the repository when migrating data.  I don't know what those are.  I couldn't find anywhere talking about this, so I would really appreciate if you can provide me what those are and the values that I need to set.

Thanks again for your help and time.


Best regards,

Chang

-----Original Message-----
From: Michael Haggerty [mailto:[email protected]] 
Sent: Tuesday, October 19, 2010 12:13 AM
To: PARK,CHANG (A-PaloAlto,ex1)
Cc: [email protected]
Subject: Re: Question on Migrating CVS Projects to SVN Single Repository

On 10/18/2010 08:02 PM, Chang Park wrote:
> I am trying to migrate multiple CVS projects to a single repository but
> each project has its own trunk, branches, and tags. For example, I have
> 2 CVS projects, /project_a and /project_b. I would like to migrate these
> 2 projects in a single repository, named REPO. 
> 
> [...]
> My questions now,
> 
> 1.  Should I create a repository, SING_REPO, first before migrating
> data? Or repository should be created during migration process such that
> when I run cvs2svn?

Usually cvs2svn creates the repository by itself, but if you want to
create the repository manually before the conversion, then use the
--existing-svnrepos option.

> 2.  In the cvs2svn doc, it says to use option file that migrate multiple
> projects at once. But example option file contains a lot more options
> than only I need. I don't know what to do other options in this file.
>  Also, I am not migrating multiple projects at once but in separate
> time.  Can I simply delete all these options and use only the portion I
> need?  What I would like to know is if there is any command without
> using option file to migrate one project at a time? 

You should *not* delete options that you don't want to change.  Many
options require that a default be set by the options file.

Rather, skim through the comments in the options file to see what
options need adjusting for your conversion.  Leave the other options
untouched.

But if, for some reason, you cannot convert the multiple projects at the
same time (why not?) then read the section "One project at a time" in
the documentation [1] and "How can I convert my CVS repository one
module at a time?" in the FAQ [2].

Michael

[1] http://cvs2svn.tigris.org/cvs2svn.html#convert
[2] http://cvs2svn.tigris.org/faq.html#oneatatime

-- 
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

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

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