Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <026101c1a45f$893b5560$0200a8c0@lifelesswks> From: "Robert Collins" To: , References: <00b301c1a45e$82614b60$81293c3e AT Obsession> Subject: Re: setup.exe command line options Date: Thu, 24 Jan 2002 09:44:36 +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: 23 Jan 2002 22:44:36.0626 (UTC) FILETIME=[88C0A720:01C1A45F] === ----- Original Message ----- From: "keith_starsmeare AT yahoo DOT co DOT uk" To: Sent: Thursday, January 24, 2002 9:36 AM Subject: setup.exe command line options > I've made some progress, but it's still (infuriatingly) not at the stage > where you can do a whole installation without dialog boxes (no offense - > they're lovely dialog boxes!), but you can certainly have *fewer* dialog > boxes! > > I'm wondering if I could submit what I have so far, and either leave some > bits #ifdef'd out (how does the undefined macro > COMMAND_LINE_OPTIONS_FULLY_IMPLEMENTED sound!?) or just miss those bits out > completely from my diff. If it compiles, and works via the GUI, it is a candidate for inclusion. I'd rather not include something #ifdef'd because it doesn't compile otherwise. > I was hoping to submit the final fully working diffs, but I'm only working > in my spare time and everytime I have a look at the latest sources they've > moved on so far.... I'm always playing catch up! I've done a lot of the > grunt work; and I'd like some feedback on what I've done. Submit what you've got, I've not seen the approach yet, so rather than you having a lot of gruntwork to do, lets get the review process happenning ASAP. Rob