Re: Best Practice for CVS user who is converting to SVN

Patrick Nelson wrote:
> In cvs your could submodule your repository like:
>
> Root repo is /var/cvs/dev
>
> tcl/tapp1
> tcl/tapp2
> tcl/tapp3
> tcl/tappn
> pl/papp1
> pl/papp2
> pl/papp3
> pl/pappn
>
> and then user the module files to call things out like:
>
> cvs co tapp1
>
> and get just the tapp1 directory.

If I understand correctly, all the modules file does is to create an
alias/shortcut, right? If so, there is no direct way in SVN to do that. What
you can do however is to read up on 'svn:externals' and install such a link
in the root of your repository. However, since there is no implicit
repository (as $CVSROOT for CVS), users are always required to specify the
complete path for the initial checkout and this does not gain that much.

> Looking at what cvs2svn did when it converted it looks like it put
> everything in one repository root of /var/svn/dev and not in sub
> projects.

I don't think it does so unconditionally. Maybe you should have given it a
different target-path for the SVN pepository?

> So it seems like I need to break all of my apps repos and
> cvs2svn them separately...

Not clear what you mean with that. Maybe you could give us an example of where
things ended up and where you wanted them to be.

Uli

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 4 11:16:25 2004