Re: Externals: Multiple definitions for the same path

Walter,

I agree that this seems like a great opportunity for Subversion to tell
folks they've done something that they probably don't mean to do. Of
course, we don't want to break existing versioned files by erroring out if
we encounter this already present. But we certainly could error out any
time a new or modified svn:externals property that violates this constraint
is about to be set on a directory.

Feel free to file an issue in our tracker if you are able to do so,
referencing this thread: http://svn.haxx.se/dev/archive-2012-09/0091.shtml

One question, though: is there any circumstance in which this functionality
could be beneficial? What happens if, say, I have an externals URL that's
referenced by one URL when I'm inside my corporate firewall, and a different
URL otherwise?

    http://internal-only.company.com/svn/repos/my/external ext-wc
    https://externals-only.company.com/svn/repos/my/external ext-wc

Does Subversion gracefully handle that, allowing the last working external
in the list to be the one that "takes"?

-- C-Mike

On 09/06/2012 11:02 AM, Walter Klust wrote:
> When setting or modifying the svn:externals property it is possible to
> specify multiple entries for the same path.
>
> Example:
>
> svn propget svn:externals trunk
>
> https://svn-server:8080/svn/multi/extfolder1 barf
> https://svn-server:8080/svn/multi/extfolder2 barf
> https://svn-server:8080/svn/multi/extfolder1 barf
> https://svn-server:8080/svn/multi/extfolder2 barf
>
> IMHO only one entry per path should be allowed.
>
> Would it make sense to implement a check in the command line client and
> issue at least a warning if someone tries to commit this kind of property ?
>
>
> Walter

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development