Ok so now my repository looks like this:
/
/trunk
/branches
/project1
/project2
/project3
And I have a property at / saying r100:VERSION_1_0
Revision 100 of what? Which one of the 4 copies of my application @ r100 represents VERSION_1_0?
That was my point when I said ... "Unless you have a trunkless/branchless repository, simply creating a textual alias for a revision number is useless". If the cheap label solution in SVN is going to work at all, it has to at least include a URL you tag. That way at least it's a label-like implementation of the cheap copy mechanism.
Cheers
Rob
> -----Original Message-----
> From: Saulius Grazulis [mailto:grazulis@ibt.lt]
> Sent: Monday, February 27, 2006 8:32 AM
> To: users@subversion.tigris.org
> Subject: Re: I, too, miss tags.
>
> On Sunday 26 February 2006 22:00, Rob van Oostrum wrote:
>
> > > The repo root could also be used for repo-wide labels.
> > >
> > > Scott
> >
> > So when searching for a tag, your wrapper script would have to traverse
> > ALL branches, and somehow figure out how to chose between duplicates?
>
> Not at all. Our wrapper should get a list of labels from root of the WC.
> Something like (could not help playing a bit):
>
> saulius@lokys labels-in-subversion/ > svn pl -v wc/
> Properties on 'wc':
> svn:labels :
> r1:INITIAL
> r1:VER-1.0
> r4:VER-1.1
>
> Now, if I tell svn-wrapper that I want revision VER-1.0, it will use r1,
> and
> if I tell that I
>
> > How would it even know where to look for these branches?
>
> At the root :)
>
> > Would this need
> > to be configurable
>
> Can be, but must not be.
>
> > ... to support different repository layouts?
>
> Add label to the directory from which one commits. Warn if the associated
> label list is empty. This will work fine with any dir layout
>
> > Also, this
> > would preclude you from cleaning up branches you no longer need to get
> > rid of some clutter,
>
> Epps... what clutter? You still think that labels are directories ;). They
> are
> not.
>
> If you do not need a temporary label, remove it -- its gone (but will
> remain
> in old revisions -- fine, the deletion must be documented). If the label
> is
> MILESTONE-RELEASE-100.1, it should probably be never deleted and will be
> flagged as such to prevent accidental/unauthorazed removal ;)
>
> > unless you don't care about losing visibility over
> > the associated tags as well.
>
> Hei, come on!
>
> saulius@lokys labels-in-subversion/ > svn pl -v wc/ | tail -n 3
> r1:VER-1.0
> r4:VER-1.1
>
> even now gives us two last labels, out of many thousands. What visibility
> loss
> are you talking about?
>
> saulius@lokys labels-in-subversion/ > svn pl -v wc/ | grep VER-1
> r1:VER-1.0
> r4:VER-1.1
>
> greps all releases of version 1, and so on.
>
> The label interface just needs to provide 'svn-labels --list'
> functionality,
> to list all labels.
>
> --
> Dr. Saulius Gražulis
>
> Institute of Biotechnology
> Graiciuno 8
> LT-02241 Vilnius
> Lietuva (Lithuania)
>
> fax: (+370-5)-2602116
> tel.: office: (+370-5)-2602556
> mobile: (+370-684)-49802, (+370-614)-36366
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 27 18:21:09 2006