That is true. You can define a svn group, and allow
those using svn access to it. So as long as they have
file access to the directory, they can create the
repository themselves. But that doesn't change the
fact that if a new project is starting or being
imported, the new Repository does need to be created.
In my opinion, it's a small step which only occurs at
the beginning. It takes very little time to create an
empty repository. And this is worth keeping changes
in one project affect the revision number of another
separate project.
--- Jean-Pierre Sevigny <jpierre@zingy.com> wrote:
>
> Yeah but then... everytime a user needs to import a
> new project, they
> need you to create a new
> repo.
>
>
>
> >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
> >it.
> >
> >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
> >specifics).
> >
> >- 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,
> >/home/svnowner/repositories).
> >
> >So, after all this, I've got a bunch of repositores
> on
> >my SVN Server.
> >
> >/home/svnowner/repositories/ProjectARepos
> >/home/svnowner/repositories/ProjectARepos
> >
> >Prople wishing to check out a project only need to
> >know the name of the Repository, which will look
> >like..
> >
> >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.
> >http://au.movies.yahoo.com
> >
>
>---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> users-unsubscribe@subversion.tigris.org
> >For additional commands, e-mail:
> users-help@subversion.tigris.org
> >
> >
> >
> >
>
>
Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 15 23:14:22 2005