> We've got most of our projects in the one repository. The only reason
> we've got multiple repositories is for vastly different areas - ie we
> have a repository for software development, and another that houses our
> server configuration files (eg the contents of /etc)
> Other than that I see no compelling reason why we would want to create
> seperate repositories for different projects.
Each of our repositories will be read/write for the group that's responsible
for that major product group, and read-only for everyone else. Our network
admin wants to set up the access rights to the various repositories using
groups under Windows and he's of the opinion that will be easier than trying
to manage it in Apache. I have to defer to his greater expertise on that
one, as I don't have much expertise at all in that area.
> If the projects are in the one repository, a new project just requires
> an svn mkdir, and that can be done by a developer rather than an admin.
We should only have a few repositories, one for each of our product groups.
Individual projects would only be created under one of those umbrellas,
allowing us to use 'svn mkdir' for the vast majority of cases. Those major
product groups have been a part of our business for years, so I don't see
much change happening there that would necessitate creating a new repository
very often, if at all.
Thanks for the response.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 25 18:03:12 2005