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 Message-ID: <3CE5372C.6030208@ece.gatech.edu> Date: Fri, 17 May 2002 13:00:28 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/00200205 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Harig, Mark A." CC: cygwin AT cygwin DOT com Subject: Re: setup.exe 2.218.2.8/9 broken References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Harig, Mark A. wrote: >>-----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. Perhaps some explanatory text on the panel where setup asks for "local directory" would be nice. Something like "This is the cygwin setup program's private cache. Do not choose a directory with pre-existing contents, unless those contents are the result of an earlier run of this setup program". Care to provide a patch? But no, it's not "the solution". Chris has already added some code that assists setup in parsing only "proper" setup.ini files and skipping non-setup.exe-related ones. > 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. Probably a good idea -- but you can also use the "scaper" utility from PCMag (ZDnet) to grab text from popup dialogs. --Chuck -- 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/