Gregoire Welraeds schrieb:
> We are in a process to migrate from source-safe to subversion.
> We have several quite seperated big projects (only a few lib
> dependencies involved).
>
> I was thinking about setting up one repository by projects or by
> "linked together" projects so that I can have a very granular
> configuration and by projects hooks script.
> Apart >from a bigger workload, is there anything else that would
> advocate for the "all together in one repository" solution?
>
- If you're dealing with an extremely large number of developers, using
seperate repositories will not have users wait for a database lock (of
course, depending on the db backend used) as often as a single big
repository would.
- Multiple smaller repositories can be distributed amongst different
servers, eg. one local server only available from machines within your
company and one public server which can also be accessed from home over
the internet
- The "all together in one repository" solution would not let you adjust
the user access rights on a per-project basis, so every department had
full access to everything or no access at all
- Using one large repository, subversion's repository-wide revision
number will even be counted up for inactive projects. Not a problem at
all, but even components with no active development will be assigned
higher revision numbers constantly (which quickly grow ridiculously
large) making it somewhat inpracticable for up-to-date checking purposes.
> TIA,
>
> Grégoire Welraeds
> //
>
-Markus-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 7 08:01:33 2005