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

Patterns for components based projects

From: Steven Woody <narkewoody_at_gmail.com>
Date: Tue, 13 Jan 2009 15:41:17 +0800


We have two or three projects developed concurrently. These projects
have some aspects similar to each other, hence they share a collection
of public components each of which gets a dedicated top source
directory for its own. I know in svn there is a mechanism sounds
something like 'external links', and I want to ensure from you experts
that this is exactly what I am looking for. Actually, I think the
challenge is after project Pa and project Pb shared component Cx,
there exits situation one day that Pa find it has to modify/improve
Cx to some extends to fits it own needs and still don't want to break
Pb which is in the meantime using original version of Cx. More
difficult than this, Cx still has a chance to find it need to
improve/modify Cx too. So my question is:

1. How to allow above development requirements to be fulfilled while
get all my code version-controlled and well managed?
2. After Pa and Pb changed Cx, Is it still easy to me to let these
chances merge back and release a more recent version of Cx for further
3. How exactly to use the 'external link' feature of SVN when in every
step of above process?

Thanks advance.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-13 08:42:13 CET

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.