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: gui-libs/egl-wayland/
Date: Tue, 28 Jun 2022 17:26:48 +0000 (UTC)	[thread overview]
Message-ID: <1656436983.f250a8be56710528ff542868ab51391d8e2e2445.ionen@gentoo> (raw)

commit:     f250a8be56710528ff542868ab51391d8e2e2445
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 28 17:21:33 2022 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Tue Jun 28 17:23:03 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f250a8be

gui-libs/egl-wayland: keyword 1.1.10

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

 gui-libs/egl-wayland/egl-wayland-1.1.10.ebuild | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/gui-libs/egl-wayland/egl-wayland-1.1.10.ebuild b/gui-libs/egl-wayland/egl-wayland-1.1.10.ebuild
index efb760761a04..15f3bab74424 100644
--- a/gui-libs/egl-wayland/egl-wayland-1.1.10.ebuild
+++ b/gui-libs/egl-wayland/egl-wayland-1.1.10.ebuild
@@ -11,9 +11,7 @@ SRC_URI="https://github.com/NVIDIA/egl-wayland/archive/refs/tags/${PV}.tar.gz ->
 
 LICENSE="MIT"
 SLOT="0"
-# unkeyworded for now as non-xwayland wayland vulkan seems to miss a symbol
-# that is likely from a yet unreleased libnvidia-vulkan-producer.so
-#KEYWORDS="~amd64 ~arm64"
+KEYWORDS="~amd64 ~arm64"
 
 RDEPEND="
 	dev-libs/wayland


             reply	other threads:[~2022-06-28 17:27 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 17:26 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-03  5:23 [gentoo-commits] repo/gentoo:master commit in: gui-libs/egl-wayland/ Ionen Wolkens
2024-09-03 12:31 Ionen Wolkens
2024-08-23  5:13 Ionen Wolkens
2024-08-09 22:34 Ionen Wolkens
2024-08-02 15:59 Ionen Wolkens
2024-07-29 16:17 Ionen Wolkens
2024-07-23 15:15 Ionen Wolkens
2024-07-18 16:44 Ionen Wolkens
2024-03-20  7:17 Ionen Wolkens
2023-11-15 19:28 Ionen Wolkens
2023-11-13  4:04 Ionen Wolkens
2023-10-18 19:47 Ionen Wolkens
2023-10-18 19:47 Ionen Wolkens
2023-08-06  4:32 Ionen Wolkens
2023-07-28 18:45 Ionen Wolkens
2023-06-08 12:45 Arthur Zamarin
2023-06-03  5:21 Ionen Wolkens
2023-06-03  5:21 Ionen Wolkens
2023-04-22  6:53 Ionen Wolkens
2023-04-22  6:53 Ionen Wolkens
2023-04-11 11:43 Ionen Wolkens
2023-03-09 20:13 Ionen Wolkens
2023-03-02 18:05 Ionen Wolkens
2022-09-09  7:21 Ionen Wolkens
2022-09-02 19:07 Ionen Wolkens
2022-09-02 19:07 Ionen Wolkens
2022-09-01  6:47 Ionen Wolkens
2022-08-11 11:35 Ionen Wolkens
2022-08-11 11:35 Ionen Wolkens
2022-08-07 13:59 Ionen Wolkens
2022-06-12 15:51 Ionen Wolkens
2022-02-14  0:48 Sam James
2022-02-14  0:48 Sam James
2021-12-28 17:10 Ionen Wolkens
2021-12-27  0:05 Ionen Wolkens
2021-12-21  0:59 Ionen Wolkens
2021-12-14 15:56 Ionen Wolkens
2021-12-14 15:56 Ionen Wolkens
2021-10-14 23:34 Ionen Wolkens
2021-09-03 23:34 Ionen Wolkens
2021-07-20  1:23 Ionen Wolkens
2021-07-20  1:23 Ionen Wolkens
2021-06-23  2:24 Ionen Wolkens
2021-06-18 17:05 Ionen Wolkens
2021-05-18 19:01 David Seifert
2021-04-17 14:44 David Seifert
2021-04-17 14:44 David Seifert
2021-04-17 14:44 David Seifert
2021-03-21 19:13 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=1656436983.f250a8be56710528ff542868ab51391d8e2e2445.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