This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: Postinstall scripts and file access issues
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 12 Aug 2004 14:18:52 -0400
- Subject: Re: Postinstall scripts and file access issues
- References: <411B86FD.74673732@phumblet.no-ip.org>
- Reply-to: cygwin-apps at cygwin dot com
On Thu, Aug 12, 2004 at 11:04:29AM -0400, Pierre A. Humblet wrote:
>Those of you that do not follow the Cygwin list should look at
>the thread <http://cygwin.com/ml/cygwin/2004-08/msg00354.html>
><http://cygwin.com/ml/cygwin/2004-08/msg00280.html>
>
>In brief, postinstall scripts can produce unreadable files,
>due to interactions between the Windows and POSIX security
>models. This is particularly the case for scripts using "cp",
>e.g. man.sh and base-files-profile.sh (among others?).
>It is probably the root cause of several complaints to the list.
>
>As a maintainer, the easy way out is to "export CYGWIN=nontsec".
>Your script will then produce files with the same permissions as
>what setup itself does, so you are off the hook.
>
>If you don't do that, then you should either "touch" the destination
>file before copying into it, or "chmod" after the copy.
>
>This should probably go into <http://cygwin.com/setup.html#postinstall>
Should we just have setup.exe set CYGWIN=nontsec and have any postinstall
script which needs it set it explicitly?
cgf