Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com List-Unsubscribe: List-Archive: List-Help: , Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Mon, 2 Aug 1999 14:06:08 -0400 From: Chris Faylor To: Anders Norlander Cc: ssiddiqi@ipass.net, Mumit Khan , cygwin@sourceware.cygnus.com, mingw32@egroups.com Subject: Re: gcc-2.95 mingw32 MSVCRT runtime fixed/updated. Message-ID: <19990802140608.A1496@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com References: <37A5DAD4.C0E9E198@hem2.passagen.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37A5DAD4.C0E9E198@hem2.passagen.se>; from Anders Norlander on Mon, Aug 02, 1999 at 07:52:20PM +0200 On Mon, Aug 02, 1999 at 07:52:20PM +0200, Anders Norlander wrote: >Suhaib M. Siddiqi wrote: >> > My basic stumbling block to releasing this right now is that I don't >> > have a full version of InstallShield here and I don't want to rely on >> > the internal group who did this last time to produce it since they are >> > notoriously slow. So, I was thinking of trying to just do something >> > with a shell script and offering the option to download individual >> > packages from the net or bundling everything up and sending a large tar >> > ball. >> > >> > So, the shell script would just ask basic questions like "what packages >> > do you want to install?", "where should I install this?" and "should >> > this be root, then?". There won't be any fancy graphics or anything. >> > >> > What do you think? >> > >> >> Personally I would prefer the Shell script to install Cygwin. It gives >> more control to user, in comparision to InstallShield. > >What about user's that don't have a shell installed? All of the necessary binaries will be part of the install package. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com