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 sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 15 Mar 2001 17:16:50 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: setup.exe busted. Please fix? Message-ID: <20010315171650.A6472@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <984686756 DOT 19199 DOT ezmlm AT sources DOT redhat DOT com> <3AB13098 DOT 3DE03E20 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AB13098.3DE03E20@ece.gatech.edu>; from cwilson@ece.gatech.edu on Thu, Mar 15, 2001 at 04:14:00PM -0500 On Thu, Mar 15, 2001 at 04:14:00PM -0500, Charles Wilson wrote: >Wait. I'm confused. latest/gcc contains source tarballs too. Is it >*setup* that's broken. setup.exe is broken. Every directory should contain a source tarball and that tarball should not be considered an "upgrade" from a previous version. What would have happened if I had chosen to upgrade ncftp was, ncftp.exe would have been deleted, and the sources would have been installed. That is clearly wrong. Older versions of setup.exe didn't work that way. I'm sure this is just a simple thinko. It is no big deal since a newer setup.exe hasn't been installed yet. cgf