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

Shared projects with svn:externals.

From: Christopher Svec <christopher_svec_at_yahoo.com>
Date: 2004-07-10 17:55:41 CEST

I have a number of related Subversion projects that use the same
sub-project via svn:externals, like this:

           svn:externals grabs SharedProject

           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:

                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?

Perhaps MasterProject could have SharedProject in its svn:externals,
and when ProjectA and ProjectB are checked out from within MasterProject,
Subversion would see that MasterProject/SharedProject already exists,
and would not checkout ProjectA/SharedProject or ProjectB/SharedProject.

With that scheme, checkout order for svn:externals might matter,
which could get ugly and annoying to manage.

Of course, if ProjectA and ProjectB use different versions of SharedProject,
it becomes an even bigger problem.

Does anyone have a development universe that looks like this? How do you
manage the projects?



Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 10 17:55:58 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.