Re: Feature request: allow for relative working copy paths in svn:externals definition

On Fri, Mar 2, 2012 at 8:14 AM, Andreas Krey <a.krey_at_gmx.de> wrote:
> On Fri, 02 Mar 2012 14:54:38 +0000, Humm, Markus wrote:
> ...
>> In my eyes nothing beats the simplicity and understandability of
>> svn:externals with one single level deep relative paths
>> to a directory above.
>
> Exactly as long as you don't try to do
>
>   svn checkout http://your/soft/ware/trunk dir-a
>   svn checkout http://your/soft/ware/trunk dir-b
>
> in one and the same directory (namely $HOME, where I do this all the
> time).
>

I got the impression that he wants that to work with a single copy of
his commonlib pulled into the parallel directory like he had checked
it out there separately. But, that misses the point of versioning.
It is common practice for the externals to be tied to specific
branch/tag or peg revisions, and also common in development for one
project to require libs at a different version than another. So,
even if you ignore the danger to non-svn files, the workspaces have to
be self-contained to protect them from each other.

-- 
    Les Mikesell
       lesmikesell_at_gmail.com