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: Sat, 10 Nov 2001 23:30:34 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Move zlib up one level? Message-ID: <20011111043034.GA22375@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20011111032226 DOT GA21492 AT redhat DOT com> <3BEDFD26 DOT 7060806 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BEDFD26.7060806@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Sat, Nov 10, 2001 at 11:23:02PM -0500, Charles Wilson wrote: > > >Christopher Faylor wrote: > >>Would there be any objections to my moving cinstall's zlib directory to >>the same level as bz2lib, i.e., making it winsup/zlib? >> >>I'd like to use some of its functionality in cygcheck.exe. > > >Yeah, but isn't cygcheck a cygwin1.dll application? Not anymore. :-) I've been asking for someone to change this for a while but I finally decided to do this myself. I'm adding package checking to cygcheck.exe right now. I wanted to get a more intelligent version of cygcheck.exe released for cygwin 1.3.5. Changing cygcheck to a mingw application has obvious benefits and I'd been meaning to add some crude package handling to it for a while. It was sort of a proof-of-concept type of thing but it works ok for a version 1. The only problem is that I had to pull a lot of code out of setup.exe. I think we need a "libutils" directory or something that will allow the sharing of setup's version handling, filename parsing, and mount table handling. The mount table stuff is almost good enough now for inclusion in a cygwin-lite type of package that was mentioned in the cygwin mailing list a while ago. cgf