>>>>> 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.
>
> "assume"?? I am trying to find a solution in which Subversion "knows". Why
> do you not want to find such a solution?
>
> I was asked to give an example of a feature Subversion is lacking, and
> gave one. You seem to agree on that, using phrases like "assume" and "try
> first".
Quite the contrary:
When NOT using the SVN non-standard-project-layout feature,
which is not supported by other VC software anyway,
then you don't have a problem.
CHeers,
>
>> Your program can also store meta information in a svn property.
>
> This is what I am proposing, only that Subversion should manage the
> properties. You put the burden of the special property handling on every
> client, when it may be implemented once in Subversion.
>
> Håkon Hallingstad
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 10 13:55:27 2006