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

Lübbe Onken wrote:
> Speaking from my experience I cannot recommend the OBR approach. Maybe
> if you have <5 projects in only one programming language.

There is a small disadvantage if you need to dump/load to upgrade
repositories to a later version. This does not happen often, but for
example there is some work going on to speed up blame, which will
require dump/load to be fully effective.

For this reason it is a good idea to keep all your repositories in one
place, so you can find them and update them easily if you ever have to.

But it's still not a good reason for OBR. As a rule of thumb I would say
that if projects are closely related, eg. separate programs that are
always released together, such as TSVN and TortoiseMerge, then keep them
in the same repository. If you have a lot of common code, then a common
repository might be a good idea too. You can't svn copy from one repo to
another, although you can use svn:externals to handle library code.
Unrelated projects are better kept in separate repositories for all the
reasons Lübbe outlined.

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org