Putting multiple projects under svn

[Ross Boylan <ro...@biostat.ucsf.edu>]

I have work scattered in a variety of cvs and rcs repositories.  I was
initially thinking I could gradually merge these into svn.  However, my
reading of the thread starting at
http://www.contactor.se/~dast/svnusers/archive-2004-02/0614.shtml is
that this operation is unsafe, because the dates of revisions must be in
the same sequence as the svn revision numbers.

Is that correct?

If so, I think I have the following options:
1) Put each project into a separate svn repository.
2) Merge all cvs and rcs projects together into a single cvs repository
tree (by stripping out just the ,v files from rcs).  Then import the
whole tree.  I'm not sure if putting "fake" stuff in the cvs respository
(i.e., other cvs trees and rcs "trees") is entirely safe.  Then convert
the whole thing to svn.

I've started using svn on one system, and I think I've made changes to
some rcs projects after I made some svn changes.  So I suppose there is
no way those two are ever going to get together.

I could also adopt a hybrid approach, in which certain clumps of work
end up in a single repository.  The problem with that is it creates a
messy mental model of where to look for a particular project.  I suppose
I could hide it to an extent through Apache rewrite rules.

Having a single repository would be my preferred route, but option 1)
above seems much less risky.  I am not contemplating any hook scripts,
so the burden of having to maintain many of them is not such a concern.

Am I being too cautious?

Any other comemnts?

Thanks.
-- 
Ross Boylan                                      wk:  (415) 502-4031
530 Parnassus Avenue (Library) rm 115-4          ross@biostat.ucsf.edu
Dept of Epidemiology and Biostatistics           fax: (415) 476-9856
University of California, San Francisco
San Francisco, CA 94143-0840                     hm:  (415) 550-1062


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Putting multiple projects under svn

[Tom Mornini <tm...@infomania.com>]

On Mar 27, 2004, at 1:15 PM, Ross Boylan wrote:

> I have work scattered in a variety of cvs and rcs repositories.  I was
> initially thinking I could gradually merge these into svn.  However, my
> reading of the thread starting at
> http://www.contactor.se/~dast/svnusers/archive-2004-02/0614.shtml is
> that this operation is unsafe, because the dates of revisions must be 
> in
> the same sequence as the svn revision numbers.
>
> Is that correct?
>
> If so, I think I have the following options:
> 1) Put each project into a separate svn repository.

This is what I've done.

The idea of one single DB that contains ALL the code I own just didn't 
sit well. :-)

After all, the URL remains identical given a single SVN root, compared 
to a single repository with the root containing one subdirectory for 
each project.

I figured when I was *completely* convinced that SVN was foolproof I 
could merge them all into a single repository without changing access 
points. That assumes, of course, that such tools will become available 
in the future.

The only downside I've noticed, and it does not currently actually 
affect me, was the need to maintain users and passwords for each 
repository.

-- 
-- Tom Mornini


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org