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

Re: Is label support in future release?

From: Danny van Heumen <danny.vanheumen_at_hccnet.nl>
Date: 2006-11-15 21:36:31 CET

Phyrefly wrote:
> It should be possible to create "complex labels" (the label
> "release_1" is rev 1 of Dir A, but rev 2 of Dir B (as rev 2 contained
> a bugfix in Dir B, and the start of work on release_2 in Dir A). Dir
> C might not be labeled at all at this point, as it's unnecessary in
> release 1. Then all SVN commands using a rev number could be fed a
> label instead, and would be a LOT simpler to use.
Good example.
This is exactly why the SVN developers haven't implemented a (CVS like)
tag/label yet. (This is my opinion and has nothing what-so-ever to do
with the developers.)

Some people would like to see a label to be an alias for a revision
number, while others would like to see it as a collection of different
files with different versions... Some would like to keep a history
record, others want to just move the tag, and some say a tag isn't
mutable at all.
(And there are more differences where this came from :P... and the same
goes for branching concepts :-s)

So, I figure that you have the following options:
1. Find at least 8 synonyms for a 'label' (like 'alias' and 'tag') and
give every synonym a slightly different functionality. (Which will
result in a rather large command line help text.)
2. Think of an alternative argument for svn that incorporates all these
functions and is easier in use than the current approach. Suggest this
to the developers and if thoroughly thought of I'm sure they will accept.
3. Create a new program or scripts which 'wraps' around svn's tools,
which gives you an easier way to work with tags, whilst not changing the
internal functionality of Subversion.

As far as I could tell, there wasn't a solution that solves all the
different concepts of a tag (or branch for that matter) and that's why
they haven't implemented any yet.

On the other hand... when someone makes a copy of a release report and
stores it in a different drawer, everyone agrees. But if one is
suggested to copy the current state of a program for safe keeping (a tag
for a program that is about to be released) to a different location,
then it's difficult/a lot of work/etc.

Looking at it from a different point-of-view:

SVN Devvers give you:
1. parameter to point to your tag --> that is the repository url which
points to the tags directory inside the repository.

People want:
1. parameter to point to your tag --> instead of using '-r <rev#>' you
use '-r <tagname>'.

What's the big difference?


(I'm going to follow this thread with great interest, and I don't mean
to insult anyone or so with this email message.)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 15 21:37:35 2006

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