John Peacock wrote:
> Issac Goldstand wrote:
>> I recently introducedan "svn:external" directory into
>> several websites which contains common code. The external link is in
>> our repository, but uses the https:// naming scheme. This works great
>> for our developers, but when updating the server, we get an error
>>
>> svn: Unrecognized URL scheme for 'https://...'
>>
>> Is it possible to remap the external link to the equivalent file:///
>> link on the working copies of the websites on the production server?
>
> Not that I'm aware of. The svn:external is a property of the working
> copy itself, so any update will replace any smart trick you could pull
> to switch to a different path.
>
> Is there some reason you can't use http:// for the svn:external path? If
> you are concerned about making this a publicly accessible link, you
> could bind to localhost only (since it appears from context that the
> repository is local to the production server at least).
>
> Is there some reason you can't install a version of svn that supports
> client-ssl on the production server (note that you could install it into
> a non-path'd location, so only the production instance would see that)?
Subversion 1.5 supports relative externals, so you can do this easily. It
doesn't remap the externals, it just uses the schema or repository root from the
working copy to construct the external URL:
http://subversion.tigris.org/svn_1.5_releasenotes.html#relative-externals
Regards,
Blair
--
Blair Zajac, Ph.D.
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-04 18:24:52 CET