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

RE: RE: How to organize a Subversion based code tree

From: André Pönitz <andre_at_wasy.de>
Date: 2005-06-03 10:35:26 CEST

McKenna, Simon (RGH) wrote:
> -> I have several projects on my SVN server but they are
> -> all within the same repository. This makes it much
> -> easier for administration, maintenance and backup.
> True, but the downside of that is:
> - All eggs in one basket, if your repo goes AWOL, all your
> projects can't commit until the problem is fixed

And it's easier to backup things as you don't have to split
a monster repository over several tapes or such.

And backups are less intrusive as you only need to lock a
single project at a time as opposed to 'everything for
half an hour'...
> - If you want to expose, convert, etc a production repo
> (e.g. BDB vs FSFS migration), it's safer to try on a
> small (non-critical) project rather than all at once, and
> later if you need to move a project out (e.g. it's dead)
> it still lives on in your single repo (unless you do some
> svnadmin svndumpfilter command line kung-fu) but if it
> has a repo of it's own you can archive and delete.
> - Harder to keep track of repository size, e.g. a neophyte
> accidentally adds a large file which shouldn't be version
> controlled...it's harder to spot on a single multi-project
> repo than on smaller per-project repositories (of course
> you need tools to view this)

Even worse, there is almost no way to get rid of accidental
commits in such projects. With one repo per project you can
just delete the whole repository for this project.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 3 10:37:45 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.