It is no more or less likely that the repository referenced in an
external would become unavailable than the main one, and not really
something that the software should be guessing about anyway. However,
subversion needs an enclosing directory to hold the metadata about the
repository in a working copy. So, I'd assume that the reason a file
external (as opposed to a directory external) must be in a directory
already checked out from the same repository is that there is nowhere to
store the metadata about some other repository for it.
David Weintraub 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.
> On Wed, Sep 30, 2009 at 6:03 AM, Gabriel SCOLAN
> <gabriel.scolan_at_sagem.com <mailto:gabriel.scolan_at_sagem.com>> wrote:
> In version 1.6.x, the following limitation on File external is
> /File externals cannot refer to files from other repositories. A
> file external's URL must always be in the same repository as the URL
> that the file external will be inserted into/
> Why does this limitation exist ? Is there an objective to remove
> this limitation in the up an coming version 1.6.x or 1.7 ?
> David Weintraub
> qazwart_at_gmail.com <mailto:qazwart_at_gmail.com>
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-30 17:45:41 CEST