RE: multiple project setup

Alessandro Sabatelli wrote:
> hi all. i'm fairly new to subversion and am not sure about best
> practices regarding multiple projects. when using cvs i tend to just
> keep everything in one repository and back up the repository as
> needed. but i'm not convinced that this is the best way to do things
> using svn (or cvs for that matter)... but this may just be the
> newness of the repository wide versioning. even though i know it's
> wrong i tend to think about the repository version as a version tag
> or changeset.

Subversion only provides a versioned filetree plus a few extras. In particular, it doesn't provide any notion of 'project', 'version tag' or 'changeset'. What it does provide is a sound base to implement these on top of it, please see the book for different approaches to this. The book also explains the hot backup script which should be used for integration into whatever backup solution you use.

> should i have a separate repository for each project? or should i
> keep them all in one repository? i can see some pros and cons to
> both approaches, but i'm wondering what people with real-world
> experience would have to say.

I personally would keep things in a single or few repository as it keeps things simple. In particular how would you handle the case where two projects are merged or one project is forked?
Anyway, using the dumpfilter utility, you can lateron still split it up in two repositories if you want, while merging is a bit more complicated if you want to do it later.

Uli

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 28 12:17:39 2005