Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <048a01c17873$64825600$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <20011128193300 DOT GA6598 AT redhat DOT com> <039901c17862$f1e80f50$0200a8c0 AT lifelesswks> <20011129011236 DOT GD9605 AT redhat DOT com> Subject: Re: Recent setup.ini corruption Date: Thu, 29 Nov 2001 12:15:52 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 29 Nov 2001 01:17:18.0344 (UTC) FILETIME=[966DE080:01C17873] ----- Original Message ----- From: "Christopher Faylor" > >I intend to have a non-mingw commandline parser for the next release of > >setup. That should allow trapping files that upset creates that setup > >cannot handle for whatever reason. > > I'm sorry, Robert. I don't know what you mean. What's a non-mingw command > line parser? A version of the parser from setup that will build for unix commandline use, and can lint setup.ini for you. Rob