Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: RE: 1.3.22: TMPDIR Initialization From: Robert Collins To: Mark Moore Cc: cygwin@cygwin.com In-Reply-To: <000a01c2fb51$7f375290$02fda8c0@fatboy> References: <000a01c2fb51$7f375290$02fda8c0@fatboy> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-At8eeIBs5AFSRmeNVZqm" Organization: Message-Id: <1049545462.3850.85.camel@localhost> Mime-Version: 1.0 Date: 05 Apr 2003 22:24:22 +1000 --=-At8eeIBs5AFSRmeNVZqm Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2003-04-05 at 18:58, Mark Moore wrote: > Robert, >=20 > If the permission on the folder pointed to by $TEMP is going to be change= d > during install, it seems to me it would be done by setup.exe. If not, wh= ere > would that operation be performed? Setup doesn't set any special permissions. It sets a generic umask and mode, and applies that throughout. ALL special permissions, scripts, and local customisations are done via post-install scripts, which run after setup extracts the package files, and before setup completes. So, if the TEMP permissions need adjusting, it's the job of a postinstall script (perhaps base-files in this case) to do that. Cheers, Rob --=20 GPG key available at: . --=-At8eeIBs5AFSRmeNVZqm Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+jsr2I5+kQ8LJcoIRAu9AAJ9M+6EP60+7nIlQUMR3G3Cv7WnQxACfaaDQ yIlQ+TdsRgst68aueLbywVg= =2wDR -----END PGP SIGNATURE----- --=-At8eeIBs5AFSRmeNVZqm--