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: setup.exe 2.218.2.8/9 broken MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 18 May 2002 10:13:56 +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: "Jon LaBadie" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4I0EHw10729 > -----Original Message----- > From: Jon LaBadie [mailto:jcyg AT jgcomp DOT com] > Sent: Saturday, May 18, 2002 4:46 AM > > Not being a PC person, are "setup.exe" and "setup.ini" the > names used by convention or is there some Windows requirement > for these names. Convention. > If convention, could situation 2 be eliminated by adding a > "cygwin" id to the name e.g. setup-cyg.ini. setup.exe > (?setup-cyg.exe?) could look for the new version > preferentially, falling back to the old if not found. Until a new piece of software - say a cygwin related tool - calls it's ini files setup-cyg.ini. I see this as an interesting idea, but fundamentally just a kludge. The real solution IMO is to * Rather than default to CWD if there is no stored preferemce default to CWD + /archive (to catch what could be a common approach of making c:\cygwin and then running setup from there. This is an approach 'taught' to folk older auto-extracting archive programs). * When the local package dir is chosen, do a scan for ini files, and if any parsing errors occur, complain at that point (and not with the parsing error), rather than when heading into the chooser. This allows us to say 'The local package dir you have chosen contains setup.exe specific files that are corrupt or invalid. Please see http://www.cygwin.com/setup-ug.html for more information'. Cheers, Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/