[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Problems with "svn status" command and NTFS junction points

From: Branko Cibej <brane_at_xbc.nu>
Date: 2004-03-02 10:55:20 CET

Quoting Ben Collins-Sussman <sussman@collab.net>:

> Boris wrote:
> > I did some additional testing and realized that the svn commit command
> > also can't handle NTFS junction points.
> If any part of svn can't handle junctions, then that's true for *all* of
> svn.
> It's not even svn at fault here... it's APR's file i/o abilities. SVN
> uses APR for all disk access. I think you guys need to take this
> question to the APR dev list and ask what's up.

I don't think it's not APR's problem. Try doing the same thing on Unix,
replacing "junction" with "szmlink". IIRC you'll get similar results. APR treats
NTFS junctions as symbolic links (which is correct), but Subversion is eminently
stupid about symbolic links, even when you don't try to make them part of the
working copy.

For example, the SVN client will barf if you move a .svn directory out of the WC
and create a symlink to it instead.

Another insteresting data point is that "svnadmin hotcopy" will igonore symlinks
in the hooks directory, which is unfortunate if you link your hook scripts in
from sonewhere else (as I do, so that I can keep the hooks in an SVN WC, guess
why :-).

In short -- it's a bug. The _reason_ for the bug is that we "don't handle
symbolic links," and we didn't bother to make the distinction between symlinks
_in_ the WC and symlinks _to_ the WC (and unversioned parts thereof). We could
fix this in 1.0.x, if the problem is serious enough.

-- Brane

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 2 10:54:37 2004

This is an archived mail posted to the Subversion Users mailing list.