From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/virtualgl/
Date: Wed, 22 Dec 2021 10:30:14 +0000 (UTC) [thread overview]
Message-ID: <1640169007.2eb93feb58f6cfed74dbcc7e5d4559039078c226.pacho@gentoo> (raw)
commit: 2eb93feb58f6cfed74dbcc7e5d4559039078c226
Author: Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 22 10:30:07 2021 +0000
Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Wed Dec 22 10:30:07 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2eb93feb
x11-misc/virtualgl: Avoid file collision with mesa-progs[egl]
Thanks-to: Edgar Dragon
Closes: https://bugs.gentoo.org/829792
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Pacho Ramos <pacho <AT> gentoo.org>
x11-misc/virtualgl/{virtualgl-3.0.ebuild => virtualgl-3.0-r1.ebuild} | 2 ++
1 file changed, 2 insertions(+)
diff --git a/x11-misc/virtualgl/virtualgl-3.0.ebuild b/x11-misc/virtualgl/virtualgl-3.0-r1.ebuild
similarity index 96%
rename from x11-misc/virtualgl/virtualgl-3.0.ebuild
rename to x11-misc/virtualgl/virtualgl-3.0-r1.ebuild
index 284d9b318933..9eaf3b90069a 100644
--- a/x11-misc/virtualgl/virtualgl-3.0.ebuild
+++ b/x11-misc/virtualgl/virtualgl-3.0-r1.ebuild
@@ -93,7 +93,9 @@ src_install() {
systemd_dounit "${FILESDIR}/vgl.service"
# Rename glxinfo to vglxinfo to avoid conflict with x11-apps/mesa-progs
+ # and eglinfo to veglinto because of conflict with mesa-progs[egl]
mv "${D}"/usr/bin/{,v}glxinfo || die
+ mv "${D}"/usr/bin/{,v}eglinfo || die
# Remove license files, bug 536284
rm "${D}"/usr/share/doc/${PF}/{LGPL.txt*,LICENSE*} || die
next reply other threads:[~2021-12-22 10:30 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 10:30 Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-20 11:21 [gentoo-commits] repo/gentoo:master commit in: x11-misc/virtualgl/ Pacho Ramos
2024-07-12 17:23 Arthur Zamarin
2024-07-12 17:23 Arthur Zamarin
2024-05-18 16:08 Sam James
2024-05-18 15:35 Sam James
2024-05-18 10:16 Pacho Ramos
2024-05-18 10:16 Pacho Ramos
2024-05-18 10:16 Pacho Ramos
2023-04-17 13:30 Pacho Ramos
2023-04-17 13:30 Pacho Ramos
2022-12-01 22:28 Jakov Smolić
2022-12-01 22:24 Jakov Smolić
2022-10-23 16:17 Pacho Ramos
2022-10-23 16:17 Pacho Ramos
2022-08-16 5:32 Joonas Niilola
2022-08-16 5:32 Joonas Niilola
2022-08-15 16:43 Andreas Sturmlechner
2022-07-10 14:39 Sam James
2022-05-22 11:04 Pacho Ramos
2022-05-22 11:04 Pacho Ramos
2022-05-04 22:32 Sam James
2022-05-04 22:32 Sam James
2021-12-21 18:25 Pacho Ramos
2021-05-08 9:27 Pacho Ramos
2021-05-08 9:27 Pacho Ramos
2021-05-08 9:27 Pacho Ramos
2021-05-01 9:53 Mikle Kolyada
2021-04-12 17:33 Sam James
2021-04-12 17:33 Sam James
2021-03-26 11:25 Sam James
2021-03-25 15:42 Sam James
2021-02-14 19:52 Sam James
2020-11-29 11:45 Pacho Ramos
2020-11-29 11:45 Pacho Ramos
2020-07-25 14:16 Pacho Ramos
2020-07-24 12:23 Sam James
2020-06-27 10:48 Pacho Ramos
2020-06-27 10:48 Pacho Ramos
2020-06-06 15:58 Pacho Ramos
2020-06-04 20:36 Pacho Ramos
2020-06-04 20:36 Pacho Ramos
2019-11-20 12:22 Andreas Sturmlechner
2019-11-19 12:48 Agostino Sarubbo
2019-11-18 11:50 Agostino Sarubbo
2019-06-05 9:19 Andreas Sturmlechner
2019-06-05 7:46 Agostino Sarubbo
2019-06-05 6:48 Agostino Sarubbo
2019-05-01 23:35 Craig Andrews
2019-01-11 21:31 Craig Andrews
2019-01-11 21:31 Craig Andrews
2018-06-09 14:15 Mart Raudsepp
2018-06-06 8:13 Andreas Sturmlechner
2017-11-07 13:17 Manuel Rüger
2017-11-02 21:16 Thomas Deutschmann
2017-10-16 3:34 David Seifert
2017-04-08 9:09 Ettore Di Giacinto
2017-04-08 9:09 Ettore Di Giacinto
2016-10-22 7:54 Pacho Ramos
2016-10-16 8:23 Pacho Ramos
2016-09-29 17:45 Pacho Ramos
2016-06-10 15:32 Agostino Sarubbo
2015-12-04 9:43 Anthony G. Basile
2015-09-20 8:23 Pacho Ramos
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=1640169007.2eb93feb58f6cfed74dbcc7e5d4559039078c226.pacho@gentoo \
--to=pacho@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