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

Re: One repository per project or one to rule them all?

From: Scott Lawrence <slawrence_at_pingtel.com>
Date: 2005-06-28 14:41:25 CEST

On Tue, 2005-06-28 at 09:27 -0300, Ben Jackson wrote:
> Currently I have all of my projects in one SVN repository. This seemed
> like a good idea at first as there were some shared code libraries that
> were used across multiple projects, but the log is getting cluttered,
> and I'm thinking it might be a good idea to split the repository by
> project. Is this a good idea? Thanks,

We made the opposite choice initially - we made each of several
libraries its own repository. We're now going through the work to merge
them again (which svn supports remarkably well, actually).

The problem we found is that it's a pain to track what rev of each
library is needed for each dependent component.

Scott Lawrence, Consulting Engineer
Pingtel Corp.  http://www.pingtel.com/
+1.781.938.5306 x162 or sip:slawrence@pingtel.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 28 14:43:56 2005

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.