Re: Error with commit/update on win32 in 5740

Philip Martin wrote:

>brane@xbc.nu writes:
>
>
>
>>I can't believe a chmod makes that much of a performance difference;
>>
>>
>
>Disk IO is always important, particularly on shared network
>filesystems. However I did measure this a few months ago and the
>difference was lost in the noise.
>

That's what I suspected.

> Things may change if the overall
>performance of the wc library improves, but at the moment it is not
>important.
>
Exactly.

>>if it does, then let's stop making the files in .svn read-only.
>>
>>
>
>On Windows perhaps, I think it's a useful feature on Unix.
>
>
If it's a useful feature on Unix, it's useful on Windows, too. If that's
the case, then we should look for the root of the "problem" (ignoring
the fact that performance measurements show it isn't one):

Windows filesystems don't allow deletion of a file if it's marked read-only.

Well then, the solution seems straightforward: Add an option to
apr_file_remove that will force the deletion even when the file is
read-only. That's a no-op on Unix and a chmod on Windows (and probably
OS/2 and Novell).

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org