X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <485C0309 DOT 7080404 AT bmts DOT com> Subject: RE: setup.exe command line parameters Date: Sat, 21 Jun 2008 14:03:47 +0100 Message-ID: <005601c8d39f$3e3cc550$2708a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <485C0309.7080404@bmts.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Ralph Hempel wrote on 20 June 2008 20:21: > Long story short, I ended up using a hacked older version of setup.exe > that accepted a -p parameter and a list of packages. It worked great! > > Is there a compelling reason why that patch can't be applied to the > current setup and released? Are there security or stability issues > I'm not thinking about? > > That being said, I CAN run setup.exe in unattended quiet mode and > get a BASE cygwin install done, and I'm quite happy with that. But > I'd really, really like to specify packages on the command line. > > Can I help by offering to update the patch to the current setup? Absolutely, yes, please! If you post it to the cygwin-apps list, with a ChangeLog entry, I'll see what we can do about getting it applied. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/