[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Separate or combined repository for multiple projects (was 'Complexity of relocate')

From: Lübbe Onken <luebbe_at_netzbeisser.de>
Date: 2005-02-19 11:59:01 CET

Albrecht Moll schrieb:

>Hi Luebbe,
Hi Albrecht,

>we are about to restructure our repositories. Currently we are planning to
>everything in one repository (mainly due to administration issues)
>What exactly do you mean with 'will work out better in the long run'?
The OBR (one big repository) approach has some advantages. You can move
any project anywhere you like inside the repository. (I can think of
only one at the moment, strange)... We started with the OBR approach,
but after six months I ripped it apart, because there were too many
disadvantages even though we had only four projects in the repository at
that time. Now we have >25.

Having your projects in one repository each has more advantages.
1) You get a revision number per project (=repository)
2) You can set up different hooks per project
3) Your repositories are smaller (backups)
4) If one repository is wedged, because a process is hanging, all the
others are still alive.
5) Administering many repositories is no work at all. It takes me 15
seconds to set up a repository and that's it.

I have written a script that creates the repository, sets up the hooks
and loads a default dumpfile which sets up the inital layout and
properties. The only other manual step involved is that I sometimes have
to add external users (freelancers) to our svn_authz file to give them
different permissions. That's all.

Speaking from my experience I cannot recommend the OBR approach. Maybe
if you have <5 projects in only one programming language.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Feb 19 12:02:05 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.