On 10/13/06, Kevin Greiner <greinerk@gmail.com> wrote:
>
> On 10/13/06, Phyrefly <phyrefly.phyre@gmail.com> wrote:
> > Firstly, I have a very large number of small projects, and I'm not
> > sure if I should be creating a lot of repositories (high overhead when
> > creating a project, but low when accessing the repos) or one big one
> > (easy to add a project, but potentially a lot of overhead when
> > updating). Does anyone have any advice on this for me?
>
> Personally, I prefer creating a single repo since it's easier to administer
> (backup, verify, dump/load are easier on a single repo) and permisions are
> now flexible enough to allow fine-grained control. A single repo also means
> the creation of a new project is very easy. Creating a whole new repo is
> harder, requiring the intervention of an admin or script on the svn server.
Kevin covered pretty much everything, but I have a followup question
here Phyrefly. Why do you think there is a "lot of overhead" when
updating a project that's part of a larger repository? If a developer
only needs one or two particular small projects, then that's all they
should check out and all they need to update. In this scenario, there
are only very rare cases where one would need/want to check out the
whole repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 13 14:39:32 2006