Message-Id: <200002242055.PAA20903@delorie.com> 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: "Parker, Ron" To: "'cygwin-developers AT sourceware DOT cygnus DOT com'" Cc: Mumit Khan Subject: RE: Installer (WAS: RE: next net release preview) Date: Thu, 24 Feb 2000 15:03:00 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" -----Original Message----- From: Mumit Khan [mailto:khan AT NanoTech DOT Wisc DOT EDU] Sent: Thursday, February 24, 2000 2:53 PM To: Parker, Ron Cc: cygwin-developers AT sourceware DOT cygnus DOT com; cgf AT cygnus DOT com Subject: Re: Installer (WAS: RE: next net release preview) > 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.