I have done a fairly extensive search of the list and the web, but have
still not found a definitive answer to this question (though there is
clearly a lot of conflicting opinion). The question is a very common one:
"Should I use a single repository for all my projects, or a separate
repository per project?". The answer, it appears is "It depends.".
So, maybe looking at a different way round, what are the pros and cons of
each approach? Here is what I have gleaned so far (pros only - cons are
asuumed to be 'unable to do the pros of the other one').
Single Repository - Pros:
* Can easily move files between projects, retaining history.
* Only one set of hooks/config files/permissions to deal with
* Can share code resources easily (though externals allow this between
multiple repositories)
Multiple Repositories - Pros:
* Smaller and easier to backup
* Can archive an old project
* Logically separates individual projects.
* Simplifies permission assignation on a per-project basis.
* Revision number is tied to the project (although I think this is probably
a bogus argument)
* Less damage done if a repository becomes corrupted
Can you add to this list?
As an aside, the SVN book appears to imply that a single repository is the
recommended approach, as all the examples use this layout. However the
following sentence caught my eye: "A common change is the decision to move
multiple projects which are sharing a single repository into separate
repositories for each project.", which implies that this approach often
turns out to be wrong... not quite sure what to make of that!
- Mark Clements
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 21 17:58:14 2006