X-Spam-Check-By: sourceware.org Date: Mon, 6 Mar 2006 11:05:51 -0500 (EST) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: "Dr. F. Lee" cc: cygwin AT cygwin DOT com Subject: Re: setup.exe: feature request with patch In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 On Mon, 6 Mar 2006, Dr. F. Lee wrote: > Hi All, > > I deploy cygwin using unattended (http://unattended.sf.net/) and wpkg > (http://www.wpkg.org/). It's useful for me to be able to specify additional > packages to be installed on the command line. The attached file is a patch to > provide this: call "setup -p package1,package2,package3,...,packageN" to have > packages1-N artificially included in the 'Base' part of the distribution and > hence automatically included. > > No doubt there are many better ways of doing this (I'm not a C++ programmer > and had to go with 'what I could do' rather than 'the best way') but perhaps > this will be useful. Frank, First off, thanks for the patch -- it's always nice seeing someone actually try to solve the problem himself, whatever the eventual outcome. However, patches to setup should generally be sent to cygwin-apps (you'd have to subscribe). FWIW, I've looked at the patch, and it seems to be doing what it promises to do (with two minor nits: the global packages_option seems superfluous, since you don't need to use it outside of package_meta.cc, and there is probably no reason to make a distinction on whether something was added via the command line or the user's selection)... Further discussion of this should happen on cygwin-apps. But, more importantly, you don't have to do *any* C++ programming at all to achieve what you want. Simply set up a local package server with one empty package, which is in Base and "requires:" all the packages you need installed. But I agree that a command-line approach might be more comfortable in some cases. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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/