Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
Subject: RE: A couple of setup.exe nits
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Thu, 28 Feb 2002 00:32:06 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA76008AAD0@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: A couple of setup.exe nits
Thread-Index: AcG/kWJXyiKyU7k9S86CLrm/QDJ8AQAAWiog
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Jason Tishler" <jason AT tishler DOT net>,
   "Cygwin-Apps" <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g1RDXZN08055



> -----Original Message-----
> From: Jason Tishler [mailto:jason AT tishler DOT net] 
> Sent: Thursday, February 28, 2002 12:23 AM
> To: Cygwin-Apps
> Subject: A couple of setup.exe nits
> 
> 
> I found the following nits with the current setup.exe:
> 
> 1. setup.exe no longer responds to Windows messages during 
> postinstall.
> 
> I noticed this because one of my postinstall scripts did a 
> SendMessage(HWND_BROADCAST, ...) which caused a deadlock 
> situation. I changed to PostMessage() to workaround the 
> problem.  Note that Task Manager also indicates a status of 
> "Not Responding".

Hmm, do we care? (Seriously, do we?/should we?)
 
> 2. /etc/setup/installed.db indicates files end with ".bz2" 
> regardless of
>    their true suffix.

Which files? The list files or the package files? If the package files, then that is purely for backwards compatability with older setup's to ensure that they still parse it correctly. The canonical package name was never used for anything that isn't present elsewhere anyway.

Rob