On 07.11.2013 10:24, Thorsten Sch├Âning wrote:
> Guten Tag Ben Reser,
> am Donnerstag, 7. November 2013 um 09:46 schrieben Sie:
>> I think nobody has put the effort into figuring out the appropriate way of
>> dealing with this. The obvious thing to do would be to fall back to the
>> current behavior if the permission isn't available.
> Subversion could fall back to using junctions if the link target is a
> directory or hardlinks if it is a file.
I think dealing with hardlinks would be a */major/* pain in the
unmentionable. They're not only hard to detect (perhaps a bit easier on
Windows than on Unix), they also share permissions (on Unix) and
read-only state (on WIndows) with the target; which is definitely
something that Subversion does not want.
I won't say a word about junctions ...
IMO it's a lot easier to just document the restriction on creating
symlinks on Windows. It's not /that/ bad; it's a (group) policy setting,
which can be managed by IT admins for large deployments. It's not as if
every user would have to fiddle with the registry or anything. We can
even have a nice error message with an URL to the appropriate MS
knowledge base article ...
Branko ─îibej | Director of Subversion
WANdisco // Non-Stop Data
Received on 2013-11-07 11:24:31 CET