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

Re: svn:externals

From: John Locke <mail_at_freelock.com>
Date: 2003-04-24 22:17:26 CEST

On Thu, 2003-04-24 at 12:54, SteveKing wrote:
> cmpilato@collab.net wrote:
> > Well, this definitely won't happen for you right now. My only
> > suggestion would be to never track HEAD in an external, either peg
> > trunk revisions or use immutable paths (like tags of the external
> > project).
> Do you think it will happen before beta? This is quite an important
> feature (at least for people in my office - they don't want to use
> subversion until that works).


Maybe this is just a matter of how you think about the repository and
the projects. What follows is (I think) just a clarification of what
cmpilato just wrote (immutable paths):

Instead of trying to automatically load your libraries in
"svn:external", how about linking specific tagged versions?

Set up a tag/ section for the shared libraries, and at appropriately
stable versions of the library, create a new tagged version.

Then in each of the projects that rely on that library, update the
svn:external property to point to the new tagged version in the current
HEAD version.

Now your development libraries remain at the tagged level, until
somebody explicitly updates the property.

Isn't this basically what you're looking for?

John Locke
Recently published: "An inexpensive e-mail server setup"
Play sports? Check in at http://teamcheckin.com
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 24 22:18:12 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.