public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/vips/
Date: Sat, 13 May 2023 09:16:39 +0000 (UTC)	[thread overview]
Message-ID: <1683969124.a848b646f698961cd14c8528e13b4f2d1ca0c00f.ionen@gentoo> (raw)

commit:     a848b646f698961cd14c8528e13b4f2d1ca0c00f
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Sat May 13 08:59:38 2023 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Sat May 13 09:12:04 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a848b646

media-libs/vips: add xorg-proto dep for USE=pango/svg/pdf

Not really used directly but results in meson error'ing out if
missing when checking for pango, cairo (also done with USE=svg),
or poppler -- or at least if pango/cairo were built with USE=X.

Unless a new EAPI adds a way for e.g. cairo to tell revdeps to pull
xorg-proto if it was built with USE=X, then not much else to do than
depend on it either way. Ultimately it's just a header-only package
and feel it's not worth risking errors over missing it.

Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 media-libs/vips/vips-8.14.2.ebuild | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/media-libs/vips/vips-8.14.2.ebuild b/media-libs/vips/vips-8.14.2.ebuild
index b0592777c293..31c28938b040 100644
--- a/media-libs/vips/vips-8.14.2.ebuild
+++ b/media-libs/vips/vips-8.14.2.ebuild
@@ -70,6 +70,9 @@ RDEPEND="
 	webp? ( media-libs/libwebp:= )"
 DEPEND="
 	${RDEPEND}
+	pango? ( x11-base/xorg-proto )
+	pdf? ( x11-base/xorg-proto )
+	svg? ( x11-base/xorg-proto )
 	test? (
 		tiff? ( media-libs/tiff[jpeg] )
 	)"


             reply	other threads:[~2023-05-13  9:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13  9:16 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-31 23:51 [gentoo-commits] repo/gentoo:master commit in: media-libs/vips/ Ionen Wolkens
2024-12-19 18:56 Sam James
2024-12-16  8:42 Ionen Wolkens
2024-11-24 15:47 Jakov Smolić
2024-11-24 11:01 Ionen Wolkens
2024-11-04 16:15 Ionen Wolkens
2024-10-19 16:53 Ionen Wolkens
2024-10-03 14:04 Ionen Wolkens
2024-09-03 12:31 Ionen Wolkens
2024-04-27 12:11 Ionen Wolkens
2024-04-03  9:14 Arthur Zamarin
2024-03-13 12:56 Ionen Wolkens
2024-02-22  6:16 Ionen Wolkens
2024-01-31 22:47 Ionen Wolkens
2024-01-29 16:47 Arthur Zamarin
2024-01-24  8:35 Michał Górny
2024-01-16  5:46 Viorel Munteanu
2024-01-10 22:02 Ionen Wolkens
2024-01-10 22:01 Ionen Wolkens
2023-12-18 18:43 Ionen Wolkens
2023-11-11 21:21 Ionen Wolkens
2023-10-27 15:20 Michał Górny
2023-10-10 20:20 Ionen Wolkens
2023-09-18 16:58 Ionen Wolkens
2023-09-12 16:15 Ionen Wolkens
2023-08-15 15:09 Ionen Wolkens
2023-08-06  4:32 Ionen Wolkens
2023-07-20 15:32 Ionen Wolkens
2023-07-14 21:32 Ionen Wolkens
2023-05-21 20:43 Ionen Wolkens
2023-05-12 10:58 Ionen Wolkens
2023-05-12  9:02 Ionen Wolkens
2018-01-28 16:29 Mikle Kolyada
2018-01-13 18:51 Ulrich Müller
2017-03-22  7:17 Michał Górny
2016-09-14 10:49 Andrew Savchenko
2016-03-20 19:12 Fabian Groffen

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=1683969124.a848b646f698961cd14c8528e13b4f2d1ca0c00f.ionen@gentoo \
    --to=ionen@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