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

Re: Shared projects with svn:externals.

From: Joerg Hessdoerfer <Joerg.Hessdoerfer_at_sea-gmbh.com>
Date: 2004-07-12 09:53:49 CEST


On Saturday 10 July 2004 17:55, Christopher Svec wrote:
> I have a number of related Subversion projects that use the same
> sub-project via svn:externals, like this:
> ProjectA/
> svn:externals grabs SharedProject
> ProjectB/
> svn:externals grabs SharedProject
> Both ProjectA and ProjectB are standalone projects. Sometimes they
> use the same revision of SharedProject, sometimes they don't.
> I also have a "MasterProject" which uses both ProjectA and ProjectB
> via svn:externals, like this:
> MasterProject/
> svn:externals grabs ProjectA and ProjectB
> When I "svn co" MasterProject, it gets a copy of ProjectA, which
> contains SharedProject, and it also gets a copy of ProjectB, which
> also contains SharedProject.
> Naive question: Is there some way to not end up with multiple copies
> of SharedProject in the MasterProject tree?

We're still thinking about how to setup such things, but what about a layout

                SharedProject/ (svn:externals)

                SharedProject/ (svn:externals)

                SharedProject/ (svn:externals)
                ProjectAMain/ (svn:externals)
                ProjectBMain/ (svn:externals)

This you could with externals without fuss, right?


Leading SW developer  - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 12 09:54:07 2004

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.