"Barry Scott" <barry.alan.scott@ntlworld.com> writes:
> > No real need to make it OS dependent, as far as I know. Windows has
> > no executable bit (using file extension for that mechanism) and Unix
> > has only the executable bit (and doesn't give a rip about file
> > extension. So I think keeping things OS-ignorant is benign.
>
> This means that you have to make sure that APR never sets the execute
> bit on not-Unix to support the client being OS independent. That's an
> obscure dependency.
Well, as it turns out, APR *does* set the execute bit, and rightfully
so (in my opinion). Keep in mind that these bits are a statement
about permission to perform tasks, not a testament to the success
you'll have if you try to do so. In other words, just because I
'chmod 777 biff.jpg' doesn't mean that trying to run 'biff.jpg' as a
program is going to work out all that well.
As is accurately noted in APR's code:
/* Read, write execute for owner. In the Win9x environment, any
* readable file is executable (well, not entirely 100% true, but
* still looking for some cheap logic that would help us here.)
* The same holds on NT if a file doesn't have a DACL (e.g., on FAT)
*/
So, the real problem here is that it seems folks want to map APR's use
of the OS's "execute permission" bit to a Subversion "execution
success" property, in what I assume is an attempt to keep from having
every new file added under Win9x from having this property set.
If that is the case, then I don't think we have any choice but to have
OS-dependent code in Subversion. That's disappointing... but then so
was Matchbox Twenty's sophomore release.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 1 04:32:12 2002