Re: changing repo layouts

On Sat, Aug 15, 2009 at 1:54 AM, Erick Calder <e_at_arix.com> wrote:

> the structure I want is: /project/trunk, /project/tags, /project/
> branches. I found the --trunk, --branches and --tags options
> available to cvs2svn but from the documentation I could not hope to
> figure out how to use these to build what I want...

Okay, we converted one project at a time, so the --branches and --tags
options allowed us to specify the location in the repository where we wanted
the branches and tags. I am not a Python developer, so I didn't bother with
the options file. However, I did find this piece of information which you
might find very handy:

<http://cvs2svn.tigris.org/faq.html#onetoone>

Or you do what I did: Write a shell script to convert one project at a time,
and specify where the trunk, tags, and branches for that project would be
using the --trunk, --tags, and --branches command line options:

for cvs_module in $CVSROOT/modules/*
do
    cvs2svn -s $cvs_module-svn --trunk /modules/$cvs_module/trunk --branches
/modules/$cvs_module/branches --tags /modules/$cvs-module/tags
done

Then use svnadmin dump and load to create a single Subversion repository.
The Subversion repository revisions will come out somewhat wacky because all
of module "A"'s transaction will come after module "B"s transactions, but it
really doesn't affect anything in the long run.

also, the man page for svnsync is rather useless, as is svnsync
> help... there isn't even really a synopsis of what this command is
> supposed to do. could you elucidate how I can use it for my purposes?
>

svnsync isn't for the conversion. It allows you to synchronize one
Subversion repository to another Subversion server instance. This second
Subversion server is a read-only instance, and can be used in remote
locations which might experience slow connections to the root repository.
Some people use it for mirroring in case the first Subversion server becomes
inaccessible. You could then use this second Subversion repository as a the
backup.

By the way, I agree the documentation is pretty bad for both svnsync and
cvs2svn. Fortunately, you only have to use cvs2svn once, and svnsync is
fairly easy to setup once you understand what it does.

-- 
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2383986
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].