Romain Prévost wrote:
>>Aha, I get it, yeah. That could be annoying. I think the only
>>solution is to solve the problem outside Subversion, by setting up
>>some sort of /etc/hosts re-mapping. This problem is also a good
>>reason why we need "relative" urls in svn:externals.
>>
>
>Ok I get it now :) Sorry for the poor advice.
>
>But wouldn't it get pretty tricky even with the relatives ?
>
Yeah - but it seems like your suggestion would get even more tricky,
wouldn't it?
It's creative, though :-)
>You'll get something as :
>
>/shared/mylib_rev2 with externals pointing to -r 2 http://lib.com/svn/lib
>/my_project pointing to http://myreposRUL/shared/mylib_rev2
>
>So modifications would only occur in the /shared directory, leaving
>the old revisions with links working ?
>
>Not sure I've been clear, neither I'm right, again :)
>
So this is like a "(adjustable) redirect"/"virtual directory"...?
As far as I can tell, this "might partially work", but would get pretty
complicated as well. I tried a few things - "cascading externals" seem
to work (referencing an external directory which itself contains
externals), BUT I can NOT reference "virtual directories" (defined by an
svn:externals).
If I understand your example correctly, the "shared" directory "really
exists" in the imported filesystem, but the "mylib_rev2" would be
defined/created by an "svn:externals"-property, right?
In that case, your second line would fail, because I cannot reference
"mylib_rev2" via svn:externals.
This might break the whole idea because I would always need one
additional directory-level.
Thanks for the help :-)
Holger
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 27 17:01:15 2005