From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Cc: pigz-cygwin-maintainer-0100@pm.me
Subject: Re: [ITP] pigz 2.8
Date: Sat, 27 Jan 2024 10:18:30 +0100 [thread overview]
Message-ID: <8a1a4489-a73e-4d53-885e-241dcff12164@gmail.com> (raw)
In-Reply-To: <3basM2VFonjRGU8Z5x8myfgYfLElV0FxoAln2BwlBHnKbRO5z2WnPZo7fUCDB7ChxmHpUgUI1s_XCUoxwKbpYu7UU7sTED8LQWk1CceNAik=@pm.me>
On 26/01/2024 22:02, pigz-cygwin-maintainer-0100@pm.me wrote:
> Hi Marco, Achim,
>
> Thank you for your time, the suggestions and fixes.
>
> Yes, looks like everything works fine with your changes.
> Also, as I understand, line `# REQUIRES="zlib"` can be removed?
you need to use REQUIRES is cygport "fails" to detect an application
requirement
$ cygport pigz.cygport deps | cat
cygwin-3.4.10-1
zlib0-1.3-1
so cygport detects a library dependency to "/usr/bin/cygz.dll"
not to package zlib, as zlib is the source package or
as binary contains only the library manual
$ cygcheck -l zlib
/usr/share/doc/zlib/ChangeLog
/usr/share/doc/zlib/FAQ
/usr/share/doc/zlib/LICENSE
/usr/share/doc/zlib/README
/usr/share/man/man3/zlib.3.gz
> I'm attaching here latest pigz.cygport with your fixes and without `# REQUIRES="zlib"` line.
>
> Best regards,
> Ihor
>
Regards
Marco
next prev parent reply other threads:[~2024-01-27 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 16:07 pigz-cygwin-maintainer-0100
2024-01-25 15:13 ` Jon Turney
2024-01-25 18:52 ` pigz-cygwin-maintainer-0100
2024-01-25 22:37 ` Marco Atzeri
2024-01-26 7:00 ` ASSI
[not found] ` <65b358c0.050a0220.5ea4e.e0daSMTPIN_ADDED_BROKEN@mx.google.com>
2024-01-26 8:12 ` Marco Atzeri
2024-01-26 21:02 ` pigz-cygwin-maintainer-0100
2024-01-27 9:18 ` Marco Atzeri [this message]
2024-01-27 14:50 ` Jon Turney
2024-01-28 0:04 ` Ihor
2024-01-28 14:34 ` Jon Turney
-- strict thread matches above, loose matches on Subject: below --
2023-11-10 1:20 pigz-cygwin-maintainer-0100
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=8a1a4489-a73e-4d53-885e-241dcff12164@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=pigz-cygwin-maintainer-0100@pm.me \
/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).