>>>> Btw: I don't want to crush all your arguments and tell you to quit
>>>> complaining, it's just that I don't have that much experience with
>>>> tagging used in company procedures etc. The scenarios I can come up
>>>> with
>>>> all seem to work in subversion. So I have to have some examples before
>>>> I
>>>> am able to see what subversion lacks. (And what subversion doesn't
>>>> quite
>>>> lack, but still is very hard to accomplish.)
>>> Make a program that lists all tags for a project (e.g. given the URL of
>>> the 'trunk').
>> svn list <trunk-url>/../tags/
>
> No, this will not work if you have layed out the project with /trunk,
> /tags and /branches in the root of the repository. The program cannot know
> your intentions without some meta-information.
Your program can assume (or try first) the standard layout.
For example, TSVN handles the tags/ and branches/
directories in a special way.
Subversion is more flexible allowing also other layouts,
but no program is forced to support all advanced features of SVN.
Your program can also store meta information in a svn property.
Or your program can locally cache the location of the tags directory.
I can understand that some people are not happy
with the command line interface of SVN tagging.
(Obviously other UIs can provide as nice UIs as they wish.)
But I don't see a problem with the tagging mechanism itself.
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 8 18:29:54 2006