This is the mail archive of the
mailing list for the Cygwin project.
mingw-zlib not available in setup.ini (Was Re: [ANNOUNCEMENT] NEW: mingw-zlib-1.1.4-4)
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- Cc: cygwin-apps at cygwin dot com
- Date: Thu, 11 Sep 2003 09:29:14 -0400 (EDT)
- Subject: mingw-zlib not available in setup.ini (Was Re: [ANNOUNCEMENT] NEW: mingw-zlib-1.1.4-4)
- References: <20030907084832.E3F556C749@redhat.com><Pine.GSO.firstname.lastname@example.org> <20030908142331.GB5065@redhat.com><Pine.GSO.email@example.com> <20030908151538.GD5065@redhat.com><3F5D4669.firstname.lastname@example.org>
- Reply-to: cygwin-apps at cygwin dot com
I noticed something unusual with the directory structure for mingw-zlib:
it's not in its own directory, but rather in a subdirectory of a new
"mingw" directory in "release". Perhaps as a consequence of that, it's
not in setup.ini (not on the mirrors I've checked, anyway). At a guess,
upset got upset at either that or something in mingw-zlib's setup.hint
(though a cursory glance doesn't show anything wrong with it).
P.S. I'm not entirely sure if this is a cygwin-apps issue...
On Mon, 8 Sep 2003, Charles Wilson wrote:
> Christopher Faylor wrote:
> > On Mon, Sep 08, 2003 at 10:30:08AM -0400, Igor Pechtchanski wrote:
> >>On Mon, 8 Sep 2003, Christopher Faylor wrote:
> >>>I don't mean to speak for Chuck but, after some discussion, it's
> >>>intended to be a separate package. The intent was to not put a zlib
> >>>directory in winsup, which would be the case with mingw-runtime. Ditto
> >>>for the gcc sources.
> >>So basically this means that everyone wanting to compile Cygwin from
> >>CVS or source tarball will have to install this package, right?
> > If they want this functionality, yes.
> Yes. Currently, the package is in the 'Mingw' group (for lack of
> anything better). I considered putting it into 'Base' for this very
> reason -- but since the cygwin utilities will no doubt link statically,
> they don't really need the DLL at runtime. Just at link time.
> But that means that zlib-mingw is no different than many other tools you
> need "for additional functionality" when building cygwin.
> gettext-devel, for recompiling the msg catalogs. texinfo, for
> recompiling the texinfo docs, and other whole suites of tools for the
> sgml documentation...
> As far as the name, there are a few packages with mingw-ish tendencies:
> Seeing no real pattern, I chose mingw-zlib.
> And yes, this is intended to be a separate package. cgf & I talked
> about simply adding the libraries to the existing zlib package, but I
> didn't like that, since I felt it would overly complicate my release
> Adding them to the existing mingw-runtime or gcc-mingw package didn't
> come up, but as cgf has already explained, that solution has its own
|\ _,,,---,,_ email@example.com
ZZZzz /,`.-'`' -. ;-;;,_ firstname.lastname@example.org
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton