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

Re: Patterns for components based projects

From: Hilco Wijbenga <hilco.wijbenga_at_gmail.com>
Date: Tue, 13 Jan 2009 09:19:49 -0800

2009/1/12 Steven Woody <narkewoody_at_gmail.com>:
> 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
> use?
> 3. How exactly to use the 'external link' feature of SVN when in every
> step of above process?

The magic phrases/keywords are "release management" and
"svn:externals". A quick search yields, e.g.,
which seems to describe exactly what you are looking for. (It's not
perfect, you shouldn't use svn:externals pointing to another trunk,
i.e. always point to a specific revision or a tag, but it should give
you at least 90% of the answer; all that's left is a bit more research
on the best practices of svn:externals.)

Received on 2009-01-13 18:20:52 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.