On Thu, Jul 25, 2013 at 1:25 PM, Thorsten Sch├Âning
> I'm working heavily with Windows junctions in my development
> environment, meaning that e.g. I check out a working copy in an
> Eclipse workspace using Subclipse and afterwards create a junction to
> my httpd cgi-bin directory. Please note that I do not link deeply into
> the working copy but create the junction to the working copy root. One
> example: The directory ...\Eclipse\Perl\some_project contains my
> working copy checked out using Subclipse, afterwards I manually create
> ...\httpd\cgi-bin\somewhere\some_project as a junction to the
> some_project folder in my Eclipse workspace.
> This allowed me to use Subclipse within Eclipse and TortoiseSVN in
> Windows Explorer depending on what I need to work on in my web
> application, which gets served by the current code base developed in
> Eclipse. This worked without any problems for years now with older
> versions of Subversion, but starting with 1.8.0 I get the following
> svn: E200007: Symbolic links are not supported on this platform
> This is not bug 4383, my client doesn't crash, it simply shows me the
> error message. Besides that, the bug's status is still new, but the
> changelog for 1.8.1 mentioned it as fixed.
Reading symbolic links on Windows Vista and later is implemented on
trunk in r1501251 :
Implement reading symbolic links on Windows Vista or later. This fix
issues with working copies located in symlinked folders.
Maybe it worth to backport this change to 1.8.x to fix reported issue?
CTO | VisualSVN | http://www.visualsvn.com
Received on 2013-07-25 12:05:23 CEST