[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: repository setup

From: Lakshman Srilakshmanan <lakshman.srilakshmanan_at_tradingpost.com.au>
Date: 2006-03-30 01:29:17 CEST



We have over 90 projects in Subversion. They are a mixture of the two
approach outlined below.


The rule of thumb I use is :- are projectA & projectB inter-related.
(ie jointed at the hip)

If there is a close dependency, such that when ever you release projectA
you will & must release projectB then it should be under the same trunk.
It is also possible that projectA & projectB may be deployed on
different machines.


There are numerous examples of this and I am not going to go into detail


On the other hand if there are no interdependency on projectA &
projectB, then it would be prudent to keep them separate for the reasons
outlined below.






From: Madan U S [mailto:madan@collab.net]
Sent: Wednesday, 29 March 2006 8:48 PM
To: Kishore Sasidharan; users@subversion.tigris.org
Subject: RE: repository setup


On Wednesday 29 Mar 2006 2:36 pm, Kishore Sasidharan wrote:
> Hi
> I have just started using Subversion. I have setup a server and have
> repository. Currently I create all projects in the same repository as
> trunk/projectA, trunk/ProjectB folders. I understand that I can also
> create different repositories for each project . Can anyone tell me
> which is the right approach and how is it advantageous.

The *right* approach is what works for you. However, whats recommended
is that
you use the following tree structure for each project...


               You can refer to this in the svn book at red-bean.com.

How is it advantageous over having multiple projects in the same repos?
Reasons that come to the top of mind right away....(these apply for
version control system)
- *all* subversion commands work faster on a smaller code base
- Permissioning becomes simpler
- easier administration (backup, branching and merging operations)
- People in project wont receive post-commit mails from checkins into
other projects (while at that, another very obvious one is that revision
numbers are shared between both projects, which isnt nice either)

   On the other hand, am not able to think of even one reason for the
method (having one repos with all project code in it). can you?

Received on Thu Mar 30 01:30:03 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.