Angelo Graziosi wrote: > Is it 'normal' that, when one installs packages, files, like *.a, *.h, > *.README etc. (i.e. files that normally are not executables), acquires the > 'x' permission ?
Yes. Just as normal as if you created the file in a regular Windows application; it will get the default ACL as defined by the standard NTFS inheritance rules (parent directory, etc.) > In the tar ball of the corresponding packages they do not have 'x'! > > Could this have to do with 'setup.exe' (I am using 2.558 snapshot) ? Setup is not a Cygwin program, it is a native Windows program. It does not contain any of the "ntsec" logic needed to map POSIX modes onto Windows ACLs. It would be a lot of duplication to reimplement all of this outside of Cygwin, and apparently it is not necessary. This is also why postinstall and preremove scripts run with the CYGWIN=nontsec environment set, so that files created there have matching semantics. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
