Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 24 Feb 2000 16:05:48 -0500 To: "Parker, Ron" Cc: "'cygwin-developers AT sourceware DOT cygnus DOT com'" , Mumit Khan Subject: Re: Installer (WAS: RE: next net release preview) Message-ID: <20000224160548.A6027@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <200002242104 DOT NAA12222 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.4i In-Reply-To: <200002242104.NAA12222@cygnus.com>; from rdparker@butlermfg.org on Thu, Feb 24, 2000 at 03:03:00PM -0600 On Thu, Feb 24, 2000 at 03:03:00PM -0600, Parker, Ron wrote: > >> I really would like to avoid touching InstallShield, especially given that >> the version I have is a GUI driven that takes forever to put together for >> packages with lots of directories and lots of files. Also, my version >> doesn't allow running an application after installation finishes (post >> install scripts are very useful). > >Agreed. I have the both InstallShield Professional and IS Express Pro. They >do allow for post installation scripts, but IS products contain numerous >bugs and as of Version 6.0 have serious backward compatibility problems. Add >to that I would like for whatever install program is used to be open source >since CYGWIN itself is and I don't want to write something for its users >that is not open source. Personally, I don't think there is any reason for the installer to be a GUI. A simple text based application that asks questions about what to install and where should be sufficient. cgf