Arch, Gnome and Systemd

Question

I'm sorry if this topic has been specifically covered elsewhere or if this is the incorrect place to ask this. I've searched and I've only found hints of it.
I'm wondering, since Gnome will now have Systemd as a dependency, if there has been any plan as to how Arch will handle it in the future. At the moment, there is a fallback mechanism to use Consolekit but I can imagine that eventually this will change. Since Systemd replaces a core component of Arch, the much-touted BSD-style init system, those wishing to install Gnome face a non-trivial task of switching to Systemd. While Arch admirably takes the stance of leaving it up to the user to handle and support him/herself in such tasks, I can nonetheless foresee maintaining good Gnome support to be an increasingly difficult task, both in maintaining a set of packages which are diverging from the Arch base in a profound way and in handling an increasing amount of non-self-helpers flooding the forum with questions.
So has any sort of discussion taken place? What can Gnome users expect in the future?
Yes, I know that Gnome doesn't fit Arch's KISS philosophy. Yes, I know that Systemd doesn't fit Arch's KISS philosophy. Yes, I know that some people here hate Gnome and love to take any opportunity to take a jab at the Gnome developers. Yes, I know that people want to complain about Lennart Poettering, Systemd, or PulseAudio. This question is strictly about future Arch policy regarding Gnome (if it is to change).
Last edited by jakobcreutzfeldt (2012-03-28 10:58:00)

Answer 1

ngoonee wrote:Since it can exist side-by-side with sysvinit I don't see the problem, honestly.
With the "it" refering to systemd, I think we have our answer. In other words, Gnome sould work fine hwere with systemd as a dependecy, and would not / should not conflict with the main arch init.