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 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: setup.exe 2.218.2.8/9 broken Date: Fri, 17 May 2002 11:01:43 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Harig, Mark A." To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4HF3GO07791 > -----Original Message----- > From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu] > Sent: Thursday, May 16, 2002 11:52 PM > To: John Haggerty > Cc: cygwin AT cygwin DOT com > Subject: Re: setup.exe 2.218.2.8/9 broken > (text deleted) > > (3) bug #2: minor issues with parsing "buried" setup.ini > files -- that > belong to things NOT cygwin-setup.exe-related. This happens > only when > someone says "My local setup directory is HERE" when HERE has > subdirectories that don't belong to cygwin-setup. (That's > bad, don't do > that: setup's 'local directory' is his own personal playground and he > doesn't play well with others) I hope that this isn't going to be the solution to the problem of setup.exe finding non-setup.exe setup.ini files. Although I don't think that I will make this mistake again, I expect that it will happen to future users who are not reading this list today. Also, I'd like to suggest that when setup.exe finds syntax errors in a setup.ini file, it log those messages in a file so that the messages can be used in reporting problems with setup.exe. I've been unable to cut&paste the text from the windows that list the parsing errors. -mark -- 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/