public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/openvdb/
Date: Wed, 23 Feb 2022 02:20:31 +0000 (UTC)	[thread overview]
Message-ID: <1645582803.787619dce77b284521aae1f46459d1a69a9c4298.sam@gentoo> (raw)

commit:     787619dce77b284521aae1f46459d1a69a9c4298
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Feb 23 02:20:03 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Feb 23 02:20:03 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=787619dc

media-gfx/openvdb: set +zlib in 8.2.0-r7

To match +blosc which needs it. Already done in 9.x.

Fixes: 31e4936280f16a043f443bd1ae004406aea34293
Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-gfx/openvdb/openvdb-8.2.0-r7.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/media-gfx/openvdb/openvdb-8.2.0-r7.ebuild b/media-gfx/openvdb/openvdb-8.2.0-r7.ebuild
index 192653b8b962..16c09bd7c6e0 100644
--- a/media-gfx/openvdb/openvdb-8.2.0-r7.ebuild
+++ b/media-gfx/openvdb/openvdb-8.2.0-r7.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/AcademySoftwareFoundation/${PN}/archive/v${PV}.tar.g
 LICENSE="MPL-2.0"
 SLOT="0/8"
 KEYWORDS="~amd64 ~arm ~arm64 ~ppc64 ~x86"
-IUSE="cpu_flags_x86_avx cpu_flags_x86_sse4_2 +blosc doc numpy python static-libs test zlib abi6-compat abi7-compat +abi8-compat"
+IUSE="cpu_flags_x86_avx cpu_flags_x86_sse4_2 +blosc doc numpy python static-libs test +zlib abi6-compat abi7-compat +abi8-compat"
 RESTRICT="!test? ( test )"
 
 REQUIRED_USE="


             reply	other threads:[~2022-02-23  2:20 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  2:20 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-18  7:26 [gentoo-commits] repo/gentoo:master commit in: media-gfx/openvdb/ Sam James
2025-04-29 19:26 Sam James
2025-04-28 21:33 Sam James
2025-04-27 23:39 Sam James
2025-02-23 22:19 Conrad Kostecki
2024-05-28 17:01 Sam James
2024-04-13 17:36 Sam James
2024-04-05  1:21 Sam James
2024-02-20 13:42 Joonas Niilola
2023-02-01 18:38 Sam James
2023-02-01  5:15 Michał Górny
2022-09-29 19:58 Matthew Smith
2022-09-25  1:27 Sam James
2022-02-28  7:06 Yixun Lan
2022-02-28  5:21 Sam James
2022-02-23  2:19 Sam James
2022-02-20 21:10 Sam James
2022-02-20 21:10 Sam James
2022-02-20 21:10 Sam James
2022-02-18 22:48 Sam James
2022-02-16 19:28 Sam James
2021-12-04  1:10 Sam James
2021-10-31  8:42 Sam James
2021-10-31  8:40 Sam James
2021-10-31  8:38 Sam James
2021-10-31  8:38 Sam James
2021-10-31  7:17 Sam James
2021-10-31  5:53 Sam James
2021-10-31  2:21 Sam James
2021-10-31  2:20 Sam James
2021-10-31  2:20 Sam James
2021-10-31  2:19 Sam James
2021-10-31  2:19 Sam James
2021-10-31  2:19 Sam James
2021-10-31  2:19 Sam James
2021-10-30 17:25 Sam James
2021-10-29 22:23 Sam James
2021-10-26 11:13 Sam James
2021-06-10  0:51 Sam James
2021-03-05 18:39 Sam James
2021-02-22  7:12 Sam James
2021-01-25 14:16 Sam James
2020-12-21 18:07 Sam James
2020-11-08 10:29 Sam James
2020-10-15 15:58 Sam James
2020-08-25 18:06 Sam James
2020-08-25 18:03 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-08-24 13:42 Sam James
2020-03-01 18:36 Matthias Maier
2020-02-09 16:29 Michał Górny
2020-01-16  6:39 Michał Górny
2019-09-13 15:43 Michał Górny
2019-06-06 20:33 Andreas Sturmlechner
2019-05-25  8:52 Mikle Kolyada
2019-03-18 22:53 Patrice Clement
2018-08-14 11:39 Jonathan Scruggs
2018-08-07 17:05 Jonathan Scruggs
2018-03-30 16:04 Aaron Bauman
2018-01-27 17:19 Jonathan Scruggs
2017-09-23  8:38 David Seifert

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=1645582803.787619dce77b284521aae1f46459d1a69a9c4298.sam@gentoo \
    --to=sam@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