On Fri, May 17, 2002 at 02:06:36PM -0400, Harig, Mark A. wrote: > > > It's the "do not choose" portion of this solution that I hope setup.exe > would avoid because it isn't paying attention to Murphy's Law. The way > setup.exe runs now there are (at least) two possible sources of errors: > > 1) setup.exe's setup.ini has become corrupted. This is well handled > by setup.exe with its display of parsing errors. > > 2) The user may have selected a Local Package Directory that contains > non-setup.exe setup.ini files. The message that is reported for this > user error (that is, 'user selected a Local Package Directory that has > non-setup.exe package files in it') is, unfortunately, the same message > as that used to report problem 1, above.
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. 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. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) -- 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/
