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

Re: Issue 1509: unable to share working copy

From: D.J. Heap <dj_at_shadyvale.net>
Date: 2004-03-19 02:31:07 CET

Ben Reser wrote:
> On Thu, Mar 18, 2004 at 11:34:25PM +0000, Philip Martin wrote:
>
>>It works on the trunk right now, I'm not planning anything else.
>>There is some question about whether r9085 is acceptable or whether it
>>needs to be changed.
>
>
> It's going to be changed. I tried making rename handle read-only files
> by making them writable, store the perms of the source file and then
> restoring them on the destination after a successful rename. I had djh
> test this last night and it won't work. There's no good way to store
> and restore the permissions on Windows.
[snip]

I haven't been following this very well, but are we talking about
read-only-ness or real security permissions? Windows has a read-only
attribute which has nothing to do with security and then real security
settings (including enforced read/write/etc permissions). The read-only
attribute is just a user-overrideable flag.

If we're talking real security permissions, then yes, I don't think APR
can do that. However, since Windows uses ACL based permissions that are
inherited automatically from the parent directory (unless configured
otherwise), is this storing/restoring actually needed on Windows?

DJ

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 19 02:31:18 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.