On Mon, 25 Nov 2019 at 03:18, Michael Catanzaro <mcatanz...@gnome.org> wrote: > > On Sun, Nov 24, 2019 at 4:23 pm, Carlos Garnacho <carl...@gnome.org> > wrote: > > If you still want to preserve X11 support, these modules do need to > > keep linking to X11 components: > > So our regular build has to continue to depend on X11 indefinitely, > because we want to build flatpaks that work under X11. And distros > certainly do as well, because they need to support X applications > indefinitely. But I don't think our VM images necessarily need to > support X applications. I suppose Javier's experiment is to see if we > can get VM images working nicely without any X stuff at all. In this > scenario, preserving X11 support is not needed.
That was, indeed, my intention; a GNOME VM only with wayland (or as little as X as possible) > > Beyond that, AFAICT if other regular GNOME session services/apps > > indirectly rely on X11 at build/runtime, it's an oversight. Well, as you can see at [1] there is a lot of oversights :) (if you see the branch as well I have to disable some apps, like gedit, that hard depend on X11 at the moment) > Well there is libgnomekbd. That seems like the main issue currently, as > it's required for core desktop functionality but still doesn't work > under Wayland. (It only works currently because it sets > GDK_BACKEND=x11.) I think more important is gcr, as a lot stuff depend on it Thanks everyone for the help reviewing patches; still quite a lot of work to do! Cheers, Javier [1] https://gitlab.gnome.org/GNOME/gnome-build-meta/issues/226 _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
