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

Re: [Subclipse-users] 2 Different SVN Locations (same repository), 1 Local Working copy

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-04-21 14:55:45 CEST

On 4/21/07, Werner Avenant <werner.avenant@gmail.com> wrote:
> My question is: is this possible? I'm pretty sure a lot of developers ran
> into this situation before, especially if they do DLL development (or just
> about any project that uses shared libraries). Is my approach wrong?
> I should also mention that I don't know CVS at all, in my searches on this
> topic one guy did mention that CVS can be very flexible. Should we switch to
> CVS to get what we are looking for?
> Thank you for your time (and patience with this long email).

The svn:externals property is designed to handle this scenario and is
what most users use. The only part of your equation it does not
handle great is giving you and old version. It can handle it however.
 What you would have to do is know the project reached a state of
maturity when you did not intend to change the base classes (for this
project) anymore. You could then change the svn:externals property to
freeze the revision you were using, with the -r option in the
property. If you do not do this, then the property will always keep
the code up to date with HEAD. This is probably what you want while
developing, but not what you want once it stabilizes.

You should also consider using tags or branches for your Base project
and pulling those in via the svn:externals property,

Here is an in-depth explanation of externals:


Mark Phippard
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sat Apr 21 14:55:51 2007

This is an archived mail posted to the Subclipse Users mailing list.