On Sun, 1 Dec 2019 at 14:53, Javier Jardón wrote:
>
> On Mon, 25 Nov 2019 at 03:18, Michael Catanzaro wrote:
> >
> > On Sun, Nov 24, 2019 at 4:23 pm, Carlos Garnacho
> > wrote:
> > > If you still want to preserve X11 support, these modules do need to
> > > keep linking to X11 components:
> >
> >
On Mon, 25 Nov 2019 at 03:18, Michael Catanzaro wrote:
>
> On Sun, Nov 24, 2019 at 4:23 pm, Carlos Garnacho
> 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,
On Sun, Nov 24, 2019 at 7:19 PM Michael Catanzaro wrote:
>
> On Sun, Nov 24, 2019 at 4:23 pm, Carlos Garnacho
> wrote:
> > Beyond that, AFAICT if other regular GNOME session services/apps
> > indirectly rely on X11 at build/runtime, it's an oversight.
>
> Well there is libgnomekbd. That seems li
On Sun, Nov 24, 2019 at 4:23 pm, Carlos Garnacho
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
c
Hi!,
On Sun, Nov 24, 2019 at 2:14 PM Javier Jardón wrote:
> Hi,
>
> This weekend I was curios about how difficult would be to have GNOME
> in a wayland-only system
>
> Thanks to building GNOME in a sandbox (thanks to buildstream and
> bwrap) and also thanks on using freedesktop-sdk as a base we
Hi,
This weekend I was curios about how difficult would be to have GNOME
in a wayland-only system
Thanks to building GNOME in a sandbox (thanks to buildstream and
bwrap) and also thanks on using freedesktop-sdk as a base we can
easily control the whole stack, so I started to experiment [1]
Not s
