[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Final(?) Relative Externals format

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-01-25 01:58:30 CET

Brian W. Fitzpatrick wrote:
> On Jan 24, 2005, at 12:18 PM, Max Bowsher wrote:
>> Relative form 3: Repository-relative
>> ///../svn/trunk/subversion/tests/clients/cmdline/svntest
>> The concept of a repository within the URL is fairly unique to
>> Subversion, and hence no suitable syntax is expressed in RFC 2396.
>> This form takes advantage of the fact that whilst the RFC explicitly
>> specifies the meaning of a relative URL beginning with zero, one, or
>> two slashes, it is silent on the matter of three or more slashes.
>> Therefore I feel this is a good way to accomodate this very useful
>> form of relativity into an unused (and unlikely to be used) void in
>> the URI standard.
> Ew. Given form 2, I think that this is unnecessary. -0.9

Things doable with this form are also doable with form 2, but it involves
hardcoding the path-to-repository on the server into the external. I.e.,
this doesn't fully solve the "repositories may move" problem, just makes it
a little less severe.

IMO, we really are overdue for some "repository root relative" notation for
use both on the command line, so it seems reasonable to do it for externals

Please clarify "Ew.".

>> Relative form 4: Directory-relative
>> ../../svn/trunk/subversion/tests/clients/cmdline/svntest
>> This form is compliant with RFC 2396.
>> It is stretching the example somewhat, since it would break on tagging
>> or branching cvs2svn, since "tags/foo" and "branches/foo" contain a
>> different number of components to "trunk", but you should get the idea
>> of what the syntax means, nonetheless.
> Seeing how fragile this is, esp. WRT tagging and branching, I'm also
> -0.9 on this.

No, this is often requested. Without it, it's impossible to make links
within the scope of a single {trunk,tags,braches} set, and have them work
properly with branching and tagging.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 25 01:59:54 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.