- cross-posted to:
- linux@programming.dev
- artixlinux@programming.dev
- cross-posted to:
- linux@programming.dev
- artixlinux@programming.dev
Some of you have probably seen the blog post a few months ago about how GNOME is more strongly depending on systemd. The changes mentioned there have landed into the latest stable versions of the mentioned software (GNOME 49) and do affect us. In particular, the main culprit is the removal of the non-systemd fallback code in gnome-session. This makes it currently impossible to launch gnome-shell/mutter on a non-systemd system. A fairly straightforward patch of using elogind, like what was previously done, no longer works either.
Since we don’t have the time or interest to write a new non-systemd codepath for gnome-session, this means that all support for gnome-based desktops has to be dropped. In particular, the affected packages would be gnome-session, gnome-shell, mutter, and gnome-settings-daemon. For now, the old versions are still in the repos but because there is so much intertwining between other gtk/gnome packages, there is no guarantee they actually work and will later be removed from our repos.
Standalone gnome applications will still continue to be packaged, but it is simply not feasible anymore to support gnome desktops without systemd.
The prob here?
Basically, a stance against IBM, GNOME and FreeDesktop, who want to push SystemD, Wayland, and PipeWire down our throats.
I take it you’re against transistioning from X11 to Wayland then?
I’ve always been against Wayland, and after I tested it, I knew problems immediately rose. My producer did the exact same thing, and realized that it was a bad idea for our workflow. My producer, Neigsendoig, and I have always needed X11 as content creators. We were also willing to try XLibre as well when that became stable.
Wayland is a protocol. The implementation depends on the window manager.
But yeah, systemd is trash and our path to hell called walled garden.