>
> SVN uses the repos as the overall version change. Like I said I don't
> know what is the best way to do projects in SVN. Is it to do a repos
> for each project or group them? If group them, then what would the
> suggested structure be?
I just set up subversion for our development group a couple of months
ago. I started with multiple projects per repository because it seemed
easier admin wise. Especially as the SVNParentPath directive had issues.
Single repository turned out to be a time consuming mistake for me
because when I decided to set up Trac (issue tracker with integration to
SVN) I needed to split the projects out to their own repositories.
Although this is possible in theory using "svnadmin dump" and
svndumpfilter, in practice svndumpfilter is problematic to say the
least. Out of about 20 projects I only managed to dump and import about
5 and they required extensive hand manipulation of the dump file.
The upshot of this is, in my opinion there is no reason to have a single
repository with multiple projects. If you have SVNParentPath in your
apache config (assuming you are using http, not sure about SVNserve) all
that needs to be done to set up a new project is "svnadmin create" and
maybe add some access control to the AuthzSVNAccessFile.
Hope that helps...
Felix
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 9 06:16:09 2004