public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/povray/
Date: Wed, 21 Jul 2021 21:57:55 +0000 (UTC)	[thread overview]
Message-ID: <1626904660.d258320fbbabe56c22b9c35ece43ad11aeb4d474.marecki@gentoo> (raw)

commit:     d258320fbbabe56c22b9c35ece43ad11aeb4d474
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 21 21:13:07 2021 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Wed Jul 21 21:57:40 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d258320f

media-gfx/povray: add slot operator for openexr

The PR originally added a new revision for this which additionally
bumped EAPI to 7 and addressed some other issues, however there are some
peculiarities in the original which ended up propagated to the new
revision and about which I am not quite sure - and in any case the
-r1 has to be pointed to :0 as well lest CI complain.

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 media-gfx/povray/povray-3.7.0.0-r1.ebuild | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/media-gfx/povray/povray-3.7.0.0-r1.ebuild b/media-gfx/povray/povray-3.7.0.0-r1.ebuild
index 0808cab1667..1813ae95f85 100644
--- a/media-gfx/povray/povray-3.7.0.0-r1.ebuild
+++ b/media-gfx/povray/povray-3.7.0.0-r1.ebuild
@@ -15,7 +15,7 @@ else
 fi
 
 DESCRIPTION="The Persistence of Vision Raytracer"
-HOMEPAGE="http://www.povray.org/"
+HOMEPAGE="https://www.povray.org/"
 SRC_URI="https://github.com/POV-Ray/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz
 	https://dev.gentoo.org/~soap/distfiles/${P}_p20160914-fix-c++14.patch.bz2"
 
@@ -30,8 +30,8 @@ DEPEND="
 	sys-libs/zlib
 	virtual/jpeg:0
 	openexr? (
-		media-libs/ilmbase
-		media-libs/openexr )
+		media-libs/ilmbase:=
+		<media-libs/openexr-3.0.0:0= )
 	tiff? ( media-libs/tiff:0 )
 	X? ( media-libs/libsdl )"
 RDEPEND="${DEPEND}"


             reply	other threads:[~2021-07-21 21:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 21:57 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-27  0:44 [gentoo-commits] repo/gentoo:master commit in: media-gfx/povray/ Eli Schwartz
2024-07-28 23:38 Sam James
2024-07-20 11:18 Arthur Zamarin
2024-03-05  4:48 Sam James
2023-12-29  0:32 Sam James
2022-10-08 19:21 Sam James
2022-08-29 18:39 Andreas Sturmlechner
2022-06-16 16:30 Sam James
2022-04-27 21:57 Andreas K. Hüttel
2022-03-01  0:01 Sam James
2022-02-28 23:58 Sam James
2022-02-28  5:45 Sam James
2022-02-28  5:45 Sam James
2022-02-28  5:21 Sam James
2022-02-15 19:51 Sam James
2021-12-06 12:15 David Seifert
2021-07-22  0:19 Marek Szuba
2021-01-24  2:23 Andreas Sturmlechner
2021-01-06 14:07 Fabian Groffen
2019-07-26 13:00 Guilherme Amadio
2018-06-08 12:20 Guilherme Amadio
2018-02-04 17:41 Andreas Sturmlechner
2016-11-19  9:25 Jeroen Roovers
2016-09-14  7:38 David Seifert
2016-07-05  8:29 Tobias Klausmann
2016-07-04 20:32 David Seifert
2016-07-04 20:22 Justin Lecher
2016-07-01  4:20 Jeroen Roovers
2016-06-10 13:53 Agostino Sarubbo

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=1626904660.d258320fbbabe56c22b9c35ece43ad11aeb4d474.marecki@gentoo \
    --to=marecki@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