Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3C56EBB3.7040700@ece.gatech.edu>
Date: Tue, 29 Jan 2002 13:36:35 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin-apps AT cygwin DOT com
Subject: Re: moratorium on new setup.exe features, please?
References: <20020129145831 DOT GA32323 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Christopher Faylor wrote:

> Can we concentrate on releasing a new version of setup.exe, please?
> 
> I'd like to eliminate the confusion that the current version of setup.exe
> is causing.  It seems like we are in a standard "add one more thing" mode
> when people are experiencing real problems and real confusion with the
> currently released setup.exe.
> 
> The only thing that I really wanted for the next release was clickable
> categories.  We have quite a bit more than that so I assume there will
> be additional unforeseen headaches coming.  This is standard when you
> add new features.  The more features you add, the more headaches you'll
> get.
> 
> So, lets just concentrate on getting something out the door which solves
> the known issues.  The biggest known issue right now is the "How do I
> install everything?"


There's one more urgent issue: I have a bzip2 and libbz2_0 package 
waiting for release, and the new setup must be able to handle that 
name(*)...I think most of these changes are in Robert's sandbox right 
now, but there's also a necessary pending patch to dump_setup.cc(?) in 
winsup/utils/

(*) sure, I could rename it, but I really would rather not...

IMO, this change is a bugfix on the current setup.exe, and not a new 
feature.  YOMV...

--Chuck