Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Subject: RE: setup's version checking MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 11 May 2002 09:41:29 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4ANfXX11040 I'll add this to the HEAD TODO list. (Nb TODO's are my short list of thigns to fix, wishlist is general ideas). Rob > -----Original Message----- > From: Christopher Faylor [mailto:cgf AT redhat DOT com] > Sent: Saturday, May 11, 2002 7:39 AM > To: cygwin-apps AT cygwin DOT com > Subject: setup's version checking > > > I don't know if anyone has noticed but, from the bug reports > in the cygwin mailing list, it seems pretty obvious that > setup isn't properly handling the version number field in setup.ini. > > What should be happening is that the version field should be > parsed first, and then, if the setup.ini version is newer > than setup.exe, a warning is raised asking the user if they > want to continue. This should happen before any further > proessing of setup.ini happens. > > What is happening instead is that the whole file is parsed > (causing all sorts of errors thanks to the md5 addition) and > then, if setup makes it that far, the user is asked if > they're sure. Unfortunately, setup doesn't make it far > enough to notify the user about the problems and so, hilarity ensues. > > cgf >