[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: Marcus Rueckert <darix_at_web.de>
Date: 2005-01-03 12:06:17 CET

On 2005-01-03 09:26:37 +0100, subversion@smartcvs.com wrote:
> 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!

that isnt a problem either. i have 2 points here:
1. normally you dont develop against trunk you release against versions.
   means you specify "you need version x.y or higher"
   that means you tag your app. and change the external to the tag of
   the library which is supported.

2. you develop against trunk and need a specific version of libX trunk.
   you can tag and point the external to the trunk@rev.

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

not really needed as you see

just my 2 cents.


irssi - the client of the smart and beautiful people
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 3 12:07:32 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.