Re: How to deal with libraries or components?

On 7/8/05, Robert Schneider <r.schneider@weingartner.com> wrote:
>
>
> Tor has responded. Is there no one else how has an idea?
> I thought this would know most people here. Or are those
> questions too off-topic?
>
> Any suggestions or hints are appreciated very much!

It's really a question of balance. Multiple repositories have higher
overhead simply because you have a certain amount of overhead
associated with each repository. Imagine if a new user came into your
group. Would it be easier to add that user to a single repository or
multiple repositories? If you modify a hook for one repository, you'd
have to do that with all the other repositories too? Which is easier?
Backing up one repository or a several dozen?

Then again, maybe you want the power to add users and hooks one
project and not another. It all depends how related the various
projects are to each other.

Multiple repositories can be placed on various servers and given to
different people to maintain. They can have different authorization
lists, different hooks, etc.

Of course, having a single repository will allow you to copy and merge
code from one project to another. With multiple repositories, you have
to use svn:externals. Then again, that might actually be a better way
of handling the code anyway because it forces people to do more
modular development.

And, a big repository will be slower and more prone to error. And when
a single big repository is down, everyone is down.

There is really no right answer. It all depends upon how related the
projects are to each other, whether you might put the various projects
on their own server in the future, and how much code is involved.

--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org