Re: Conflict resolution (gtk, wayland)

[Rutger Helling]

I've created a patch to update Mesa on staging, along with removing
wayland-egl from it. I can confirm I can still start GNOME on Wayland
manually after rebuilding with this patch.

Should I apply this to staging now? It's been two weeks since the last
commit to staging, and a merge doesn't seem to be happening anytime
soon.

On an unpleasant side-note, certain things are completely broken on
GNOME on Wayland with staging. Menus and buttons don't work anymore. I
suspect this is because our mutter and gnome-shell packages are too old
(3.24.x instead of 3.28.x).

On Thu, 17 May 2018 16:13:28 +0200
address@hidden (Ludovic Courtès) wrote:

> Hi,
> 
> Rutger Helling <address@hidden> skribis:
> 
> > It's because Wayland recently absorbed libwayland-egl. See:
> > https://lists.freedesktop.org/archives/wayland-devel/2018-April/037767.html
> >
> > Specifically:
> > "libwayland-egl is now part of libwayland, and will presumably be
> > removed from mesa in the not too distant future."  
> 
> Thanks for the info.
> 
> On our next MESA update, we should probably explicitly remove
> libwayland-egl from MESA if upstream hasn’t done it yet.
> 
> Ludo’.

0001-gnu-Mesa-Update-to-18.0.4.patch
Description: Text Data

pgp3LJrmNTP1I.pgp
Description: OpenPGP digital signature