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

Hello,

We tried a solution with junctions now (using a sysinternals junction
tool which works under XP already).
Server side in the repository all is well, but in the working copy it
doesn't work as intended as Tortoise SVN
gives us a faliure messaage on our checkin.

What did we do?

We have this structure:
D:\Test\Projekt1
D:\Test\Common

We created a Junction inside D:\Test\Projekt1 named
D:\Test\Projekt1\JunctionTest which points to
D:\Test\Common

so D:\Test\Projekt1\JunctionTest does exist as a hard link. Everything
you insert there
will turn up in D:\Test\Common and vice versa. Works fine with Windows.

Now we created some folders on the server:

/Projekt1/trunc
/Common/trunc

We defined a svn:externals on D:\Test\Projekt1 with these parameters:
Local directory is JunctionTest and URL on the server points to
/Common/trunc

Tortoise SVN accepted that.

We added everything below Projekt1 except JunctionTest to the repository
which worked fine
as the repro browser clearly shows.

We separately added everything from Common to the repository so it went
to /Common/trunc

In the repository (repro browser) we can see now that JunctionTest links
to /Common/trunk

But in the working copy we cannot get this to work. A commit on Projekt1
via Tortoise SVN
doesn't take the externals into account and a update on Projekt1 ends in
a failure message:
(translated from german)
Externals failed d:\Test\Projekt1\JunctionTest
Failure d:\Test\Projekt1\JunctionTest already exists and is no directory

Best regards

Markus Humm

ebm-papst Mulfingen GmbH & Co. KG
Sitz der Gesellschaft: Bachmuehle 2, D-74673 Mulfingen
Kommanditgesellschaft Sitz Mulfingen: Amtsgericht Stuttgart HRA 590344
Komplementaer: Elektrobau Mulfingen GmbH, Sitz Mulfingen, Amtsgericht Stuttgart HRB 590142
Geschaeftsfuehrung: Hans-Jochen Beilke (Vorsitzender), Thomas Borst, Hans Peter Fuchs, Dr. Bruno Lindl, Thomas Wagner
Received on 2012-03-02 16:21:52 CET