From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libv4l/
Date: Tue, 12 Dec 2023 23:48:30 +0000 (UTC) [thread overview]
Message-ID: <1702424894.ab3ce48858534a9189961d1a4399e2df38de3797.chewi@gentoo> (raw)
commit: ab3ce48858534a9189961d1a4399e2df38de3797
Author: James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 12 23:40:23 2023 +0000
Commit: James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Tue Dec 12 23:48:14 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab3ce488
media-libs/libv4l: Don't allow dev-qt/qtopengl to have USE=gles2-only
I had handled the older gles2 flag, but not gles2-only. media-tv/v4l-utils is
still wrong, but we'll be last-riting it before long anyway.
Closes: https://bugs.gentoo.org/919794
Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>
media-libs/libv4l/libv4l-1.26.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/media-libs/libv4l/libv4l-1.26.0.ebuild b/media-libs/libv4l/libv4l-1.26.0.ebuild
index 2913916767cc..550c6a1bd084 100644
--- a/media-libs/libv4l/libv4l-1.26.0.ebuild
+++ b/media-libs/libv4l/libv4l-1.26.0.ebuild
@@ -34,7 +34,7 @@ RDEPEND="
qt5? (
dev-qt/qtcore:5
dev-qt/qtgui:5
- dev-qt/qtopengl:5[-gles2(-)]
+ dev-qt/qtopengl:5[-gles2-only(-),-gles2(-)]
dev-qt/qtwidgets:5
media-libs/alsa-lib
virtual/opengl
next reply other threads:[~2023-12-12 23:48 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 23:48 James Le Cuirot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-24 15:03 [gentoo-commits] repo/gentoo:master commit in: media-libs/libv4l/ Arthur Zamarin
2024-09-23 9:42 Arthur Zamarin
2024-09-23 9:22 Arthur Zamarin
2024-09-23 9:13 Arthur Zamarin
2024-09-23 9:13 Arthur Zamarin
2024-09-23 0:39 Sam James
2024-09-23 0:39 Sam James
2024-07-30 22:01 James Le Cuirot
2024-07-29 21:39 James Le Cuirot
2024-07-29 20:47 James Le Cuirot
2024-07-29 20:47 James Le Cuirot
2024-07-26 19:11 Sam James
2024-07-26 19:11 Sam James
2024-07-26 19:11 Sam James
2024-07-26 14:12 Arthur Zamarin
2024-07-26 14:12 Arthur Zamarin
2024-07-26 14:12 Arthur Zamarin
2024-07-26 14:12 Arthur Zamarin
2023-12-12 23:48 James Le Cuirot
2023-03-18 23:38 James Le Cuirot
2022-04-02 13:55 James Le Cuirot
2022-04-02 12:04 Arthur Zamarin
2022-04-01 6:53 Arthur Zamarin
2022-03-31 19:37 Arthur Zamarin
2022-03-28 6:53 Agostino Sarubbo
2022-03-28 6:51 Agostino Sarubbo
2022-03-27 1:07 Sam James
2022-03-27 1:07 Sam James
2021-10-24 20:22 James Le Cuirot
2021-08-02 12:33 Marek Szuba
2021-01-05 20:51 Sam James
2021-01-03 12:10 Sergei Trofimovich
2021-01-03 11:51 Sergei Trofimovich
2021-01-03 9:14 Sam James
2020-12-29 23:15 Sam James
2020-12-29 21:24 Sam James
2020-12-27 22:58 Sam James
2020-12-27 22:39 Sam James
2020-08-23 16:42 James Le Cuirot
2020-05-28 22:24 James Le Cuirot
2020-05-02 12:40 David Seifert
2020-03-11 23:50 Andrey Utkin
2019-08-19 11:37 Agostino Sarubbo
2019-08-14 17:59 Aaron Bauman
2019-08-14 8:53 Agostino Sarubbo
2019-08-12 18:22 Andrey Utkin
2019-06-06 7:14 Agostino Sarubbo
2019-06-05 18:23 Andrey Utkin
2019-06-05 18:23 Andrey Utkin
2019-04-09 14:36 Mikle Kolyada
2019-03-11 18:05 Andrey Utkin
2019-02-28 20:22 Lars Wendler
2019-02-26 18:36 Alexis Ballier
2019-02-26 18:36 Alexis Ballier
2018-07-28 0:49 Mikle Kolyada
2018-01-13 12:16 Alexis Ballier
2017-12-08 22:49 James Le Cuirot
2017-05-30 10:54 Alexis Ballier
2017-04-25 12:58 Alexis Ballier
2017-04-25 12:58 Alexis Ballier
2017-03-16 8:36 Michael Weber
2017-01-31 16:06 Jeroen Roovers
2017-01-20 11:05 Agostino Sarubbo
2017-01-17 14:24 Agostino Sarubbo
2017-01-15 15:50 Agostino Sarubbo
2017-01-11 10:35 Agostino Sarubbo
2016-07-25 19:25 Michael Palimaka
2016-06-26 18:30 Markus Meier
2016-06-19 14:39 Tobias Klausmann
2016-06-17 13:39 Alexandre Rostovtsev
2016-03-15 2:52 Mike Frysinger
2016-03-15 2:33 Mike Frysinger
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=1702424894.ab3ce48858534a9189961d1a4399e2df38de3797.chewi@gentoo \
--to=chewi@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