Use of relative externals

[Simon Large <si...@googlemail.com>]

Hi all,

Relative externals are not documented yet in the svn book nightly, so
I have to ask here for clarification :-)

../    relative to the parent directory of the external

Presumably I can go up several levels (../../../project/dir/subdir).
Can I go above the repository root and back down into another
repository? (../../../../repos2/project/dir)

^/     relative to the repository root

Again, is this restricted to the same repo, or can I access other
repositories in the same SVNParentPath?
^/../repos2/...

//     relative to the URL scheme

This just protects against a change of access method (http -> https) ?

/      relative to the server's hostname

Can't think of any stupid questions to ask about that :-)

Simon

-- 
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Use of relative externals

[Blair Zajac <bl...@orcaware.com>]

Mark Phippard wrote:
> On Sun, Apr 27, 2008 at 5:05 AM, Simon Large
> <si...@googlemail.com> wrote:
> 
>>  //     relative to the URL scheme
>>
>>  This just protects against a change of access method (http -> https) ?
> 
> The opposite (although I might be reading you wrong).  The idea here
> is that people with write access are using https:// and people with
> read access are using http://.  With full URL's you cannot handle this
> really well.  This allows the scheme to change based on the scheme
> used for checkout.

It sounds like you're both saying the same thing here.

>>  /      relative to the server's hostname
>>
>>  Can't think of any stupid questions to ask about that :-)
> 
> Reading the release notes, I now see that the text for this one and
> the previous is wrong.  What this one adds to the above, is that it
> allows the scheme and hostname to vary.  Picture someone on internal
> network that uses svn://internal-host and someone on outside that uses
> https://external-host.

The example resulting absolute URLs in the scheme-relative and hostname-relative 
examples for the svn+ssh base URL was incorrect, I fixed this in r30805.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<bl...@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Use of relative externals

[Mark Phippard <ma...@gmail.com>]

On Sun, Apr 27, 2008 at 5:05 AM, Simon Large
<si...@googlemail.com> wrote:

>  Relative externals are not documented yet in the svn book nightly, so
>  I have to ask here for clarification :-)
>
>  ../    relative to the parent directory of the external
>
>  Presumably I can go up several levels (../../../project/dir/subdir).
>  Can I go above the repository root and back down into another
>  repository? (../../../../repos2/project/dir)
>
>  ^/     relative to the repository root
>
>  Again, is this restricted to the same repo, or can I access other
>  repositories in the same SVNParentPath?
>  ^/../repos2/...

My understanding (you'd probably want to just try it) is that Yes you
can do this.  This is really just client-side URL transformation so I
do not think it matters that it would cross a repository root, and I
recall your example as being desired functionality.

In the release notes:

http://subversion.tigris.org/svn_1.5_releasenotes.html#externals

Your second question is even given as an example.

>
>  //     relative to the URL scheme
>
>  This just protects against a change of access method (http -> https) ?

The opposite (although I might be reading you wrong).  The idea here
is that people with write access are using https:// and people with
read access are using http://.  With full URL's you cannot handle this
really well.  This allows the scheme to change based on the scheme
used for checkout.


>  /      relative to the server's hostname
>
>  Can't think of any stupid questions to ask about that :-)

Reading the release notes, I now see that the text for this one and
the previous is wrong.  What this one adds to the above, is that it
allows the scheme and hostname to vary.  Picture someone on internal
network that uses svn://internal-host and someone on outside that uses
https://external-host.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org