Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Subject: Re: bug in setup.exe for postgresql-7.3.4-1 From: Robert Collins To: Jason Tishler Cc: Max Bowsher , cygwin AT cygwin DOT com, Seth Rubin In-Reply-To: <20030805113503.GD2044@tishler.net> References: <00bb01c35a16$9057cf40$5400a8c0 AT starfruit> <20030804122611 DOT GC564 AT tishler DOT net> <01dd01c35b42$e5670910$017c883e AT starfruit> <20030805113503 DOT GD2044 AT tishler DOT net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-tTY1t2EGc8d2L303zlxo" Message-Id: <1060083416.1101.22.camel@localhost> Mime-Version: 1.0 Date: 05 Aug 2003 21:36:57 +1000 --=-tTY1t2EGc8d2L303zlxo Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2003-08-05 at 21:35, Jason Tishler wrote: Well, given the brief feedback on my request, I can only really guess. My WAG is that setup needs the cygwin ntsec acl conversion logic ported to it, along with some method to determine whether it should use it or not. Cheers, Rob --=20 GPG key available at: . --=-tTY1t2EGc8d2L303zlxo Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA/L5bYI5+kQ8LJcoIRAgVbAJ9DkJ9Kj3zG2JW+EQ1BoJjmaUz7XwCdH2Se enMSHLoRnRa63Xm08Iw7+rY= =CBel -----END PGP SIGNATURE----- --=-tTY1t2EGc8d2L303zlxo--