[Mesa-dev] [Bug 99987] Mesa 13+ breaks Xvnc (and similar X servers)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99987

--- Comment #15 from Dennis Schridde <devurandom at gmx.net> ---
(In reply to Pierre Ossman from comment #14)
> b) If it is indeed a fallback, why is that needed? I.e. why isn't Mesa being
> chosen? It does not seem robust and future proof to rely on a fallback
> mechanism. Which leads to...

Because libglvnd tries to be vendor neutral (i.e. not tied to either Mesa nor
Nvidia) and there might be other vendors providing a software / indirect
rendering implementation. Maybe not now and on current Linux distributions, but
e.g. on another OS or in the future.

> c) What happens when both Mesa and NVIDIA wants to install the fallback
> symlink? It sounds like things will just stop working, getting us right back
> to the situation that GLVND was supposed to solve.

I was wondering about the same thing. The env-var solution actually seems
superior to having a file collision between different packages. Even a config
file might be better than a symlink.

But Hans is already working on this:
https://bugzilla.redhat.com/show_bug.cgi?id=1413579#57
> I will prepare an update to add this to the Fedora mesa pkgs, but I
> need to coordinate this with the rpmfusion packages, since those currently add
> such a symlink to the nvidia libGLX.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170314/596f5f59/attachment.html>