On 1/24/08, Dave Lawrence <dlawrence_at_ad-holdings.co.uk> wrote:
> James Wilson wrote:
> > On Jan 23, 2008 4:19 AM, Dave Lawrence <dlawrence_at_ad-holdings.co.uk> wrote:
> >> You should be aware that a Cygwin build of svn.exe is NOT the same as a
> >> "normal" windows build. Here are some of the differences:
[...]
> >> * checked out files will all be made "executable" by svn windows, on
> >> cygwin only files with svn:exectuable will be executable
> >>
> >
> > Thanks, I was unaware of those differences, but they all seem to make
> > sense, except for the executable setting -- that kinda sucks and seems
> > more like a bug than a feature.
>
> Well I think Unix convention is that files aren't executable by default
> so this behavior is kind of consistent with other programs. I think
> files that are executable are automatically given this property when
> added - except when added by Windows clients (otherwise everything would
> have that property).
Historically, MS Windows did not have an executable permission on
files. If the file was readable and an extension of .exe (or .com or
one of a few others), it could be executed. At some point, to increase
security, the "Read & Execute" security attribe was added. For
backward compatability, it is common for this attribute to be set 'on'
bt default. For what it is worth, note that in MS Windows execute
permission implies read permission. While in Unix/Linux/Posix, a file
can be unreadable but still be executable. This is possible because it
is the OS itself that reads the file for the purpose of execution. The
user need not be able to read it for the OS to run it on the user's
behalf.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-24 18:49:59 CET