From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: [ITA from Yaakov] zlib
Date: Wed, 13 May 2020 23:17:55 -0400 [thread overview]
Message-ID: <295e744155e2acfc52f976b0e5c971ab15439213.camel@cygwin.com> (raw)
In-Reply-To: <4665a106-fb7e-1a6a-0615-61813ac8d1d5@cornell.edu>
On Wed, 2020-05-13 at 09:04 -0400, Ken Brown via Cygwin-apps wrote:
> There's no need for a new release, but I've made some trivial updates to the
> cygport file (attached) and checked that the build works.
This is fine. FYI at some point you might want to investigate whether
to move to the minizip fork currently packaged in Fedora, but as
nothing in Cygwin currently uses it, there's no rush.
https://github.com/nmoinvaz/minizip
https://src.fedoraproject.org/rpms/minizip/blob/master/f/minizip.spec
--
Yaakov
prev parent reply other threads:[~2020-05-14 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 13:04 Ken Brown
2020-05-14 3:17 ` Yaakov Selkowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=295e744155e2acfc52f976b0e5c971ab15439213.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).