From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] minizip
Date: Sat, 16 May 2020 17:40:38 +0200 [thread overview]
Message-ID: <7b294a2f-6073-9dcb-01af-cc3a5fe46c44@gmail.com> (raw)
In-Reply-To: <315481e4-b591-0433-d8bb-6fd11402bb26@cornell.edu>
On 16.05.2020 00:48, Ken Brown via Cygwin-apps wrote:
> cygport file attached.
>
> This is a followup to Yaakov's suggestion in
>
> https://sourceware.org/pipermail/cygwin-apps/2020-May/040049.html
>
> After I've uploaded this, someone should move all the minizip stuff
> under zlib on sourceware to the new minizip directory. Or else that
> should be done first, I'm not sure which. I guess the only question is
> whether calm will complain if it's done in the wrong order.
>
> Ken
May be you want to correct this point
$ file minizip.cygport
minizip.cygport: ASCII text, with CRLF line terminators
my build complained.
I added minizip to the package list and I am checking the new
directory structure, as we need to move from
$ find ../zlib -type f -name "*mini*"
../zlib/libminizip-devel/libminizip-devel-1.2.11-1.hint
../zlib/libminizip-devel/libminizip-devel-1.2.11-1.tar.xz
../zlib/libminizip-devel/libminizip-devel-1.2.8-3.hint
../zlib/libminizip-devel/libminizip-devel-1.2.8-3.tar.xz
../zlib/libminizip1/libminizip1-1.2.11-1.hint
../zlib/libminizip1/libminizip1-1.2.11-1.tar.xz
../zlib/libminizip1/libminizip1-1.2.8-3.hint
../zlib/libminizip1/libminizip1-1.2.8-3.tar.xz
../zlib/minizip/minizip-1.2.7-1.hint
../zlib/minizip/minizip-1.2.7-1.tar.bz2
../zlib/minizip/minizip-1.2.8-1.hint
../zlib/minizip/minizip-1.2.8-1.tar.bz2
to
$ find . -type f
./minizip/libminizip-devel/libminizip-devel-2.9.2-1.hint
./minizip/libminizip-devel/libminizip-devel-2.9.2-1.tar.xz
./minizip/libminizip2.5/libminizip2.5-2.9.2-1.hint
./minizip/libminizip2.5/libminizip2.5-2.9.2-1.tar.xz
./minizip/minizip-2.9.2-1-src.hint
./minizip/minizip-2.9.2-1-src.tar.xz
./minizip/minizip-2.9.2-1.hint
./minizip/minizip-2.9.2-1.tar.xz
./minizip/minizip-debuginfo/minizip-debuginfo-2.9.2-1.hint
./minizip/minizip-debuginfo/minizip-debuginfo-2.9.2-1.tar.xz
before an upload.
And wait for a full reindex, otherwise calm will complain anyway.
Regards
Marco
next prev parent reply other threads:[~2020-05-16 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 22:48 Ken Brown
2020-05-16 15:40 ` Marco Atzeri [this message]
2020-05-16 18:12 ` Ken Brown
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=7b294a2f-6073-9dcb-01af-cc3a5fe46c44@gmail.com \
--to=marco.atzeri@gmail.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).