From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: The Man <squishypinkelephant@gmail.com>
Cc: Vivien Kraus <vivien@planete-kraus.eu>,
74522@debbugs.gnu.org,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#74522] [PATCH 20/73] move libgl provider from mesa to libglvnd+mesa
Date: Wed, 27 Nov 2024 10:45:30 +0900 [thread overview]
Message-ID: <87bjy1la9x.fsf@gmail.com> (raw)
In-Reply-To: <97ab7e5e4d844698f520d9be0f7a3a058b16a501.1732504868.git.squishypinkelephant@gmail.com> (The Man's message of "Sun, 24 Nov 2024 21:41:13 -0600")
Hello,
Is this how Mesa upstream foresees all of its users to use it? Or is it
just Nvidia's or systems requiring of proprietary nvidia/amd drivers
(non-mesa ones) that benefit from that?
Since even nvidia is moving toward having proper free drivers (coupled
with proprietary firmware blobs...), I wonder if libgl still has value,
especially for a system such as Guix which promotes software freedom.
I haven't researched the question, so I'm asking in case you can shed
light on this matter.
Without looking too much into it yet, perhaps this change could be
mostly automated via some 'git grep -l bmesa | xargs sed
's/\bmesa\b/libgl/' or similar; and could then be committed as a single
change, eschewing the usual GNU ChangeLog format for the command used?
We allow this when the change is a massive and automated (e.g.,
sed-authored) change.
Thank you!
--
Maxim
next prev parent reply other threads:[~2024-11-27 1:47 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 3:38 [bug#74522] [PATCH 00/73] Moving Guix to libglvnd The Man
2024-11-25 3:40 ` [bug#74522] [PATCH 01/73] move libgl provider from mesa to libglvnd+mesa The Man
2024-11-25 3:40 ` [bug#74522] [PATCH 02/73] " The Man
2024-11-25 3:40 ` [bug#74522] [PATCH 03/73] " The Man
2024-11-25 3:40 ` [bug#74522] [PATCH 04/73] " The Man
2024-11-25 3:40 ` [bug#74522] [PATCH 05/73] " The Man
2024-11-25 3:40 ` [bug#74522] [PATCH 06/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 07/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 08/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 09/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 10/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 11/73] " The Man
2024-11-25 5:18 ` Liliana Marie Prikler
2024-11-25 21:33 ` The Man
2024-11-25 23:00 ` [bug#74522] [PATCH 00/73] Moving Guix to libglvnd Noé Lopez via Guix-patches via
2024-11-27 3:59 ` The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 12/73] move libgl provider from mesa to libglvnd+mesa The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 13/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 14/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 15/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 16/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 17/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 18/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 19/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 20/73] " The Man
2024-11-27 1:45 ` Maxim Cournoyer [this message]
2024-11-27 3:41 ` The Man
2024-11-27 3:46 ` The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 21/73] " The Man
2024-11-26 23:04 ` Mark H Weaver
2024-11-25 3:41 ` [bug#74522] [PATCH 22/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 23/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 24/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 25/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 26/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 27/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 28/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 29/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 30/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 31/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 32/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 33/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 34/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 35/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 36/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 37/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 38/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 39/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 40/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 41/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 42/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 43/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 44/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 45/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 46/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 47/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 48/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 49/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 50/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 51/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 52/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 53/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 54/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 55/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 56/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 57/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 58/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 59/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 60/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 61/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 62/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 63/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 64/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 65/73] " The Man
2024-11-25 3:41 ` [bug#74522] [PATCH 66/73] " The Man
2024-11-25 3:42 ` [bug#74522] [PATCH 67/73] " The Man
2024-11-25 3:42 ` [bug#74522] [PATCH 68/73] " The Man
2024-11-25 3:42 ` [bug#74522] [PATCH 69/73] " The Man
2024-11-25 3:42 ` [bug#74522] [PATCH 70/73] " The Man
2024-11-25 3:42 ` [bug#74522] [PATCH 71/73] " The Man
2024-11-25 3:42 ` [bug#74522] [PATCH 72/73] move libgl provider from mesa to libglvnd+mesa TEMP The Man
2024-11-25 3:42 ` [bug#74522] [PATCH 73/73] move libgl provider from mesa to libglvnd+mesa The Man
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=87bjy1la9x.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=74522@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=squishypinkelephant@gmail.com \
--cc=vivien@planete-kraus.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.