> From: Branko ÄŒibej <brane_at_wandisco.com>
> Date: Sun, 29 Sep 2013 07:14:07 +0200
> This is not in fact a bug in Subversion
> The solution that jiggles the security descriptor is not acceptable.
I note that svn is not touching the place where the inherit is
actually assigned (a directory), yet it is interfering with it. This
isn't a nice thing to do on Windows. It is nearly introducing an
"inconsistency" in the file system. Just my opinion, but I feel that
any time this occurs on Windows may be a bug. Whatever you call it, the
effect on the user is the same. Actually, I thought it was a bug in the
Windows OS until I came across the blog post I referenced.
(If this all doesn't shock you, you might not be a Windows programmer!)
If you want to be permissions agnostic on Windows, then I think you
will want the file to end up with the default creation permissions,
instead of arguably inconsistent ones that arise from the move gotcha.
I think this would be an improvement from being permission hostile in
this case, and ease scenarios which I hope should be valid, such as
running a web server against parts of the working copy. Like svn, most
Windows programs do not concern themselves with permissions. The
right thing" just happens by default. The solution Ivan mentioned of
creating a temp file in the same directory as the final file is common
(e.g., Microsoft Office. See "Data Integrity" and "Saved Files (Same
Directory as the Saved File)" in
http://support.microsoft.com/kb/211632). That way, of course, has its
pros and cons, too.
There are numerous ways to address this. Crossing fingers that some of
them are deemed acceptable and worth the effort. I did file issue #4432
as instructed. (Sorry about the double spacing due to me guessing wrong
about how that text box worked.)
Thanks for your consideration. I will be happy to answer any questions
you might have.
Received on 2013-09-29 16:07:20 CEST