Barry Scott wrote:
> Use of "cp" and the tags directory is an attempt to provide in svn a
> feature
> like labelling in other SCM tools. I don't think its good enough and
> others in
> this discussion don't think its good enough. You are right that I cannot
> solve
> the lack of a label feature in my gui if its not in svn in the first place.
>
> Barry
Hi,
I am currently using (experimenting with) an approach to this by
not using "svn cp /trunk/foo /tags/TAG_XY/foo" but instead i use
an extension (actually ruby script) where i specify
svn.rb cp --tag /trunk/foo --tagname TAG_XY -m "logmessage"
which automatically selects /tags/TAG_XY/foo as its target
and additionally appends an entry to a global "Tags"
file located in the repository/tags/ root.
i.e. my personal extensions "--tag" and "--branch"
add an entry like
T --rev 2234 --src "/trunk/foo" --dst "/tags/TAG_XY/foo"
--description "logmessage"
to the file %repos%/tags/Tags
and additionally put that as a property to "/tags/TAG_XY/foo"
which allows to 'search' inside the tags folder for this
special property.
this solves at least a few of my requirements.
but it has many disadvantages,
- breaks if someone renames a folder inside /tags
breaks if someone uses native svn access to
change anything inside /tags or /branches
- always copies the whole source folder content,
does not allow tagging of single files
- searching gets slower with each added tag.
- searching for/through properties is slow.
- increments the revision number multiple times
(to cp, change the property and to modify the Tags file)
i.e. its not atomic any more.
- a.s.o.
I'd be happy if all this could be built into subversion
itself, would be atomic, safe, portable to others, ...
:-)
======
c.a.t.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 5 01:54:01 2004