I don't see a huge deal about multiple repositories.
It can be configured in such a way where only the SVN
owner (the user owning the accounts) will be aware of
I've set up a Linux box the following way (I'm sure it
can be done on Windows, I just don't know the
- Built/installed SVN
- Created a user (svnowner). The home directory for
this user is /home/svnowner
- Created a directory /home/svnowner/repositories.
- Created groups, assigned access privileges, etc (I
can provide more details if necessary.... I found some
good info on the web on how to set it up).
- Create the new SVN repositories in the repositories
directory. In your case, you could create an SVN
Repository for each project.
- I use svnserve to allow remote access. I'm sure
WebDAV will work as well. You can configure svnserve
so it knows to look in a particular directory for the
repositories (in this case,
So, after all this, I've got a bunch of repositores on
my SVN Server.
Prople wishing to check out a project only need to
know the name of the Repository, which will look
svn co svn://LinuxBox/ProjectARepos/trunk
Semantically, I don't see that as being any different
to what they would use if they were all in the same
repository... (svn://mfg/group1/projectA/trunk, using
your example). I wouldn't know as a svn consumer
whether the repository is being shared with other
projects or not.
If they ever did need to share files, you can link in
external references to other repositories, if that's
needed. However, I don't think they work the same as
repository fines in regards to branching and tagging.
I think this would be useful if the external files
were being used the revisioned files, irrespective of
their tag/branch. But I could be wrong there.
Find local movie times and trailers on Yahoo! Movies.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Feb 14 23:25:19 2005