Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Tue, 24 Jul 2001 11:26:52 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: SETUP WIZARD FOR CYGWIN?XFREE86 Message-ID: <20010724112652.G9776@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <001201c11440$f5acf5a0$806410ac AT local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <001201c11440$f5acf5a0$806410ac@local>; from robert.collins@itdomain.com.au on Tue, Jul 24, 2001 at 11:02:56PM +1000 On Tue, Jul 24, 2001 at 11:02:56PM +1000, Robert Collins wrote: >Installing the logic behind an existing mature packaging system into >setup.exe however, will prevent us from reinventing the wheel - and that is >the _general_ direction I'm interesting in coding towards. I don't know >exactly what Chris thinks - but he has mentioned avoiding new wheels as well >:}. I'm a big proponent of newfangled wheel avoidance except where the avoidance means massive amounts of work. Incorporating rpm (and it would have to be rpm, sorry) into setup.exe is a huge task. It's interesting that everyone who bitterly objects to us reinventing the wheel is "too busy" to do it the "right way". Welcome to the Cygwin version of an open source project. cgf