From: "Lars Wendler" <polynomial-c@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/zlib-ng/
Date: Mon, 22 Mar 2021 08:59:11 +0000 (UTC) [thread overview]
Message-ID: <1616403465.18b0451c9ae2db037d996b0a5156ba41bf9d1f5a.polynomial-c@gentoo> (raw)
commit: 18b0451c9ae2db037d996b0a5156ba41bf9d1f5a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 18 00:01:36 2021 +0000
Commit: Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
CommitDate: Mon Mar 22 08:57:45 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18b0451c
sys-libs/zlib-ng: add blocker on sys-libs/zlib when using compat mode
Warn users if USE=compat is enabled and also include a link
to upstream's interpretation of what USE=compat provides.
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Lars Wendler <polynomial-c <AT> gentoo.org>
sys-libs/zlib-ng/zlib-ng-2.0.1-r1.ebuild | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/sys-libs/zlib-ng/zlib-ng-2.0.1-r1.ebuild b/sys-libs/zlib-ng/zlib-ng-2.0.1-r1.ebuild
index c00074bbf78..29181862229 100644
--- a/sys-libs/zlib-ng/zlib-ng-2.0.1-r1.ebuild
+++ b/sys-libs/zlib-ng/zlib-ng-2.0.1-r1.ebuild
@@ -18,6 +18,8 @@ IUSE="compat ${CPU_USE[@]} test"
RESTRICT="!test? ( test )"
+RDEPEND="compat? ( !sys-libs/zlib )"
+
src_prepare() {
cmake_src_prepare
@@ -67,3 +69,15 @@ src_configure() {
cmake_src_configure
}
+
+src_install() {
+ cmake_src_install
+
+ if use compat ; then
+ ewarn "zlib-ng is experimental and replacing the system zlib is dangerous"
+ ewarn "Please be careful!"
+ ewarn
+ ewarn "The following link explains the guarantees (and what is NOT guaranteed):"
+ ewarn "https://github.com/zlib-ng/zlib-ng/blob/2.0.x/PORTING.md"
+ fi
+}
next reply other threads:[~2021-03-22 8:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 8:59 Lars Wendler [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-07 15:43 [gentoo-commits] repo/gentoo:master commit in: sys-libs/zlib-ng/ Arthur Zamarin
2025-04-07 8:49 Sam James
2025-04-07 6:56 Sam James
2025-04-07 6:56 Sam James
2025-03-07 18:48 Sam James
2025-02-23 12:22 Jakov Smolić
2025-02-12 5:48 Sam James
2025-01-01 19:33 Sam James
2025-01-01 19:33 Sam James
2024-08-29 3:15 Sam James
2024-07-15 2:23 Sam James
2024-05-28 12:35 Sam James
2024-03-04 10:24 Sam James
2024-02-19 7:50 Sam James
2024-01-23 5:07 Ionen Wolkens
2024-01-14 2:30 Sam James
2024-01-14 2:30 Sam James
2023-11-30 3:07 Sam James
2023-10-20 0:51 Sam James
2023-06-29 8:39 Sam James
2023-06-17 3:15 Sam James
2023-06-16 1:42 Sam James
2023-06-16 1:27 Sam James
2023-03-17 22:00 Sam James
2023-03-17 21:54 Sam James
2023-02-28 12:12 Yixun Lan
2023-02-26 19:28 Arthur Zamarin
2023-02-26 17:33 Arthur Zamarin
2023-02-26 17:08 Arthur Zamarin
2022-10-07 19:58 Sam James
2022-10-02 0:14 Sam James
2022-10-02 0:14 Sam James
2022-01-01 4:29 Sam James
2021-06-26 21:32 Lars Wendler
2021-06-12 10:35 Lars Wendler
2021-05-14 7:48 Lars Wendler
2021-03-24 7:51 Lars Wendler
2021-03-22 8:59 Lars Wendler
2021-03-22 8:59 Lars Wendler
2021-03-22 8:59 Lars Wendler
2021-03-17 10:08 Lars Wendler
2021-03-17 8:23 Lars Wendler
2021-03-17 7:37 Lars Wendler
2021-03-17 7:37 Lars Wendler
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=1616403465.18b0451c9ae2db037d996b0a5156ba41bf9d1f5a.polynomial-c@gentoo \
--to=polynomial-c@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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