On Wed, Sep 30, 2009 at 11:25 AM, David Weintraub <qazwart_at_gmail.com> wrote:
> The issue is quite simple: What if that remote repository is no longer
> available or the server to the external repository has changed? What if that
> remote repository upgraded to a new version of Subversion that isn't
> compatible with your client? You might get to a point where it is now
> impossible to checkout and build your project.
>
> You also now have the responsibility of your Subversion client suddenly
> having to access another repository which will probably require different
> credentials or be using a different protocol.
Those were not really the reasons as they all had to be solved when
directory externals were implemented. Maybe you were not aware that
feature supports external repositories?
It basically came down to that the people that were interested in
doing the work did not have a need for different repositories and more
importantly there was a desire to implement the feature internally
using svn switch. So that some of the issues that exist with
directory externals did not apply. For example, there are no issues
with doing an atomic commit of the file external with other files.
Basically, by using switch the feature mostly just worked out of the
box and there was just a small amount of work to do to implement it.
I suspect that implementing it using any other technique would have
dragged in complications as you do not have that nice directory
boundary to break up things like internal editor drives.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2402142
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-30 17:48:55 CEST