Bug#812530: ITP: libglvnd -- Vendor-neutral OpenGL dispatch layer

[Timo Aaltonen]

On 02.02.2017 12:21, Timo Aaltonen wrote:
> On 02.02.2017 10:20, Timo Aaltonen wrote:
>> On 19.01.2017 11:19, Timo Aaltonen wrote:
>>> On 13.01.2017 22:56, Luca Boccassi wrote:
>>>> On Mon, 2016-12-12 at 18:14 +0200, Timo Aaltonen wrote:
>>>>> 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.
>>>>
>>>> FYI: looks like Fedora is planning to enable GLVND by default, so there
>>>> should be useful information popping up for us as well from that trial:
>>>>
>>>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BTA5ZIBD4LP6EXK6A4V4WWK7HGZTKEUU/
>>>
>>> Yep, I'll look at the packaging and extra patches they carry after next
>>> week.
>>
>> libglvnd git is now updated, have a look.. It's split again since
>> there's no way to avoid that.
>>
>> I have a weird issue bootstrapping mesa, where rebuilding it fails to
>> install libva-dev, which pulls in some bits of the previously built mesa
>> which depend on libglvnd. I hope it's just not using my local repo
>> properly..
> 
> Note that the -dev package situation will likely change still.. and the
> mesa changes will be worked on 'glvnd-wip' branch on mesa.git (not
> pushed yet). And GLES1 is dropped.

Have a look now. I'd like to upload libglvnd soon so that it gets past
NEW. Once we know what version of mesa will switch over some
Breaks/Replaces (libegl1-mesa-dev, libgles2-mesa-dev, libgl1-mesa-dev)
will be added to libglvnd-dev.


-- 
t