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

Ulrich Eckhardt wrote:

>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.
>
>
>
>I don't think it does so unconditionally. Maybe you should have given it a
>different target-path for the SVN pepository?
>
>
>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.
>
>

Your right about the modules file. I was using it to explain the way we
have used cvs. If there is a way to continue the grouping then we would
if not we would investigate more. One way we thought about was naming
the module like:

tcl-app1
tcl-app2
tcl-app3
tcl-appn
pl-app1
pl-app2
pl-app3
pl-appn

----
The way I called cvs2svn was:
 cvs2svn -s /var/svn/dev /var/cvs/dev
This created 1 repository with all the apps in it, which was not 
necessarily the way we wanted it.   So and to answer your second 
question we did called cvs2svn like:
LangList="tcl pl"
tclList="app1 app2 app3 appn"
plList="app1 app2 app3 appn"
for Lang in LangList; do
 for Mod in ${Lang}List; do
  cvs2svn -s /var/svn/dev/$Mod /var/cvs/dev/$Lang/$Mod
 done
done
This gave us separate repositories for each of our apps which will work 
and keeps them separate from each other.  Is this the best way to do it?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org