From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] libGL: consider devirtualizing
Date: Sat, 19 Dec 2020 23:45:32 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27286@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
New issue by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/27286
Description:
`libGL` and friends being virtual gives some [unexpected behaviour](https://www.reddit.com/r/voidlinux/comments/kgeyvf/opengl_no_longer_working_after_a_clean_install/). Two options:
1) fix virtual package selection in xbps (how? who?)
2) make things easier/saner by getting rid of vpkg where possible. After all, `libglvnd` exists exactly for this purpose, that is avoiding multiple conflicting libGL library files. Vendors should use the `libglvnd` mechanism.
Option 2 means:
- Current `libGL` providers have to be removed: `nvidia340` (EOL) and `sunxi-mali` (?)
- New proprietary GL implementations not using `libglvnd` won't be accepted.
Thoughts?
@q66 @abenson
next reply other threads:[~2020-12-19 22:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 22:45 st3r4g [this message]
2020-12-19 22:50 ` abenson
2021-01-20 20:32 ` ericonr
2021-01-20 20:32 ` ericonr
2021-01-20 21:33 ` st3r4g
2021-01-20 21:36 ` ericonr
2021-01-20 21:45 ` st3r4g
2021-01-20 21:46 ` st3r4g
2021-01-20 21:47 ` st3r4g
2021-01-20 21:47 ` st3r4g
2021-01-20 21:49 ` st3r4g
2021-01-20 21:49 ` ericonr
2021-01-20 21:50 ` ahesford
2021-01-20 21:56 ` ericonr
2021-01-21 14:48 ` ahesford
2021-01-21 14:55 ` ericonr
2021-01-21 15:32 ` ericonr
2021-01-21 15:49 ` ahesford
2021-01-21 16:17 ` ericonr
2021-01-21 18:00 ` ahesford
2022-05-01 2:14 ` github-actions
2022-05-16 2:07 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27286@inbox.vuxu.org \
--to=st3r4g@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).