Daniel Lohmann <daniel.lohmann@informatik.uni-erlangen.de> writes:
> Hi everybody,
>
> One of the things I really do like on subversion is the svn:externals
> property which is in many ways a lot more flexible as the CVS modules
> concept. However, one point really makes me headaches: svn:externals
> requires to give an absolute URL to the external repository, which
> does not contain just the path, but also the protocol to use and (for
> some protocols) even the username. This is bad, as different users
> should be able to access the compount project by different
> protocols. Take for instance a projectA that contains a svn:external
> link to another projectB. All internal project team members access
> the repository using the svn+ssh protocol, but external project team
> member use https via WebDAV. Is there any way to set the svn:external
> link in a way, that it resolves to an svn+ssh://... link for internal
> team members, but to a https://... link for external team members?
> Maybe using environment variables in the external definition?
>
> How do you solve these kind of problems?
This is http://subversion.tigris.org/issues/show_bug.cgi?id=1336.
We totally agree this is a shortcoming in the externals feature :-).
There's even a patch in the issue, in fact. I've put it in 1.5, which
is a while away, but at least is not forever. We're not able to
address every issue/patch as soon as we would like, sorry for that.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 23 20:40:00 2005