> From: Elliott Hughes [mailto:enh@jessies.org]
>
> The main annoyance is this: as mentioned in
> [http://subversion.tigris.org/faq.html#multi-proj], "'svn
> cp/mv' currently
> only works within a single repository". This is a real bummer
> if you went
> for the one-repository-per-project option. Why isn't there an
> issue in the
> issue tracker for this? (If there is, and I just couldn't find it, why
> isn't there a link from the FAQ?)
IMHO, there are two main reasons. The first reason is that the svn:external
feature makes it quite convenient to have one copy of any "infrastructure"
code shared among projects that live in other repositories.
The second reason is one that we've been coming up against in our software,
namely that the "separate repository for each project" organization works
less well than you'd think. In practice, having a bunch of projects in one
repository has little or no additional overhead. But if they share *any*
code, it suddenly becomes annoyingly awkward, as exporting a particular
version and other operations become operations on multiple repositories.
Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 7 15:59:02 2005