Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gary R. Van Sickle" To: Subject: RE: Scriptable start.exe Date: Tue, 5 Feb 2002 22:13:14 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20020206040148.GF12007@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > -----Original Message----- > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of Christopher Faylor > Sent: Tuesday, February 05, 2002 10:02 PM > To: cygwin AT cygwin DOT com > Subject: Re: Scriptable start.exe > > > On Tue, Feb 05, 2002 at 09:55:04PM -0600, Gary R. Van Sickle wrote: > >> So I am wondering what the state of making start.exe scriptable > is? This is > >> a feature that would be quite helpful on a current project so that clients > >> can install a properly configured cygwin without the few clicks that are > >> required now. > > > >None of the people that have been working on setup.exe recently (including > >myself) appear to have any desire to add any scripting functionality to it. > >There's much more important work that needs to be done before such a notion > >could even be realistically considered. > > Currently, setup.exe is simple enough that you could almost get by with > just using shell scripts, tar, and bzip2. > One probably could. Exercise left to the reader ;-). I can forsee at some distant point in time maybe some command-line functionality thus: setup.exe packagename which I think has essentially (or maybe even exactly) already been suggested. But one release at a time. Speaking of which... Rob? ;-) -- Gary R. Van Sickle Brewer. Patriot. -- 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/