Bug#812530: ITP: libglvnd -- Vendor-neutral OpenGL dispatch layer
On 12.12.2016 17:47, Andreas Beckmann wrote:
> On 2016-12-08 13:31, Timo Aaltonen wrote:
>> It's there now, but we're still uncertain if mesa will switch to use it
>> in stretch, and I don't know how nvidia driver migrating to it without
>> mesa would work?
>
> I don't plan to switch to the packaged libglvnd without mesa adopting it
> as well. Also in the current form (everything in a single package) I
> cannot use it as a drop-in replacement for the glvnd libraries from
> nvidia (where I follow a strict one library per package scheme).
> For the mesa side the question will be: will it be a complete switch
> over or will there be the possibility to switch between non-glvnd and
> glvnd based libGL etc.? NVIDIA currently provides both variants for
> libGL and libEGL, since the glvnd variants have shown some regressions
> (but I don't know in which applications). For the nvidia driver I
> provide both variants with the glvnd variant being the preferred
> alternative.
It's a configure switch so in theory mesa could be built with glvnd and
without (two separate builds), but I doubt we'll do that.
> Please keep the Debian NVIDIA Maintainers in the loop if there is
> progress being made on the MESA side.
Yep, and I'm not sure if it was a good idea to put everything in one
package. Also, this probably should be kept out of stretch and instead
spend some more time on it.
I'll look into it some more after xmas. Do you have an irc channel I
could join at some point?
--
t
Reply to: