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

Re: svn:externals and shared projects

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-29 14:41:04 CEST

On Aug 29, 2006, at 10:26, Sander van der Wal wrote:

> A quick question about using svn:externals and multiple libraries
> Lets say I have project A, library B and Library C. These are all
> separate
> folders in a repository, with the usual layout. There is a need for
> B and C
> to be different projects, project D also uses B and C, and project
> F uses C
> too.
> In this case, Project A uses library B and Library C. Library B
> also uses
> Library C.
> If I use svn:externals to connect B and C to A and C to B, I think
> I would
> get the following folder structure in the sandbox.
> Project A
> docs
> src
> library B | folder pulled in because of svn:externals mapping B
> to A
> docs
> src
> Library C | folder pulled in because of svn:externals
> mapping C to B
> docs
> src
> Library C | folder pulled in because of svn:externals mapping C
> to A
> docs
> src
> i.e There are two copies of Library C in the sandbox.

There sure are. :-)

As I see it, your options are:

1) Accept it. Project A uses Library B and its copy of Library C, and
Library B uses its copy of Library C.

2) Project A knows that Library B includes Library C, so Project A
only includes Library B via externals and uses Library B's copy of
Library C.

3) Library B doesn't include Library C but requires that the project
into which it's included does so, and Library B then accesses the
copy of Library C available one level higher.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 29 14:44: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.