Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Date: Tue, 29 Jan 2002 13:38:15 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: moratorium on new setup.exe features, please? Message-ID: <20020129183815.GA5247@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20020129145831 DOT GA32323 AT redhat DOT com> <3C56EBB3 DOT 7040700 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C56EBB3.7040700@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Tue, Jan 29, 2002 at 01:36:35PM -0500, Charles Wilson wrote: >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/ I've checked in a fix for this but I expect that it won't be necessary when setup.exe is released. I'll probably be linking some kind of library from cinstall or something. cgf