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

Re: Relative externals - take 2

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-01-04 15:52:32 CET

John Peacock wrote:
> Max Bowsher wrote:
>> 4. Scheme-relative externals.
>> Returning to our module1 example use cases, suppose that module1 now
>> wishes to use module8, which is being developed by Beta Group within the
>> same organisation.
>> Both repositories are visible over both http:// and https:// - but,
>> whichever you use for the root checkout, you probably want to use for
>> externals too.
>> RFC1808 defines a syntax for us to use:
>> "module5 //beta.example.com/repositories/five/trunk"
> Unfortunately, this conflicts with SVK's usage (that's a path in the
> default
> repository). I don't know if this is enough reason to forbid its usage in
> Subversion itself, but there it is...


My example above is the RFC1808 officially defined way to specify a scheme
relative URL.
I'm really unenthusiastic about deviating from the standard.

SVK //paths are never used in externals definitions, though, are they?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 4 15:55:08 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.