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

Re: cvs modules feature missing in subversion

From: <subversion_at_smartcvs.com>
Date: 2005-01-03 09:26:37 CET

Imagine following situation. There is an open source library LibX (e.g.
hosted on sourceforge - if it would support svn), which is used in an
application A.

Now you want to tag project A to mark your version 1.0. You want to tag
LibX, because it is part of your project and you want to be able to get
exactly this state after some months of progress. This is the point of
view from project A. From the LibX' point of view, it should not be
tagged, because - well - imagine all applications using that library
would tag it! What a mess!

I see only one reasonable possibility: integrate a copy of LibX ('
sourcecode) into your project and tag that.

But to be honest, CVS supports that as good as Subversion - it doesn't.
One has to synchronize the original LibX and the copy of it in project A

Marcus Rueckert wrote:
> hi,
> On 2004-12-31 01:16:17 -0800, Shurik O wrote:
>>svn:externals is out of the question as it wouldn't support branching and 
> why doesnt it support branching and tagging? you just need to update the
> externals in the tag/branch if needed. that doesnt sound like much work.
> darix
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 3 09:27:10 2005

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.