On Sunday 26 February 2006 10:37, Konrad Rosenbaum wrote:
> > As a prototype, a wrapper script would do. A good thing about a wrapper
> > script is that it does not need any change in Subversion itself. Also,
> > one could continue to use the usual svn client, in cases one does not
> > need labels (like everyday commits and updates). If there are no
> > intrinsic difficulties with the concept of labels, maybe some day it
> > makes its way to the svn itself... ;).
> I've experimented with such a script using revision properties.
Could I (we) have a look at it?
> The problem
> here is that subversion does not support searching for a property, so the
> script has to do the search. Unfortunately it needs about .5 to 2 seconds
> for each revision on a remote repository - doing that eg. on the KDE
> repository (currently at 513726) this would need about 3-12 days(!!) to
> search a tag.
Hmmm. What if we store a whole list of labels and corresponding revision
numbers in some property, say "svn:labels", of the repository root?
(Repository property would be preferable, but AFAIK Subversion does not have
them at the moment).
Since all labels would be stored in one property, a label per line, listing
and searching would be fast and efficient.
One could also easily create labels for sibdirectories, if one chose so :)
> A "svn propfind"(*) and "svn propgetall"(**) would help tremendously! If
> those commands were available the user could invent as many tag- and
> label-styles as he/she pleases and noone would need to implement something
> (*)list all revisions that have a property
This would be fast and only require a working copy.
> (**)dump all instances of the property
This would become unnecessary since the latest set of labels would be always
stored in HEAD revision's property.
Seems like doable, no?
Dr. Saulius Grazulis
Institute of Biotechnology
tel.: office: (+370-5)-2602556
mobile: (+370-684)-49802, (+370-614)-36366
Received on Sun Feb 26 12:58:09 2006
- application/pgp-signature attachment: stored