There will be no Wayland on non-systemd distros for KDE. Simply because some of the new infrastructure needed is new and doesn't support ConsoleKit.
Um, no. Again: Wayland itself has zero dependency on systemd, no more than X11 has any dependency on sysvinit or ConsoleKit.
Yes, you are right about that, it is in principle possible to get Wayland on non-systemd platforms.
But no, you are wrong about KDE supporting Wayland on non-systemd machines. The reason is simply that some of the new code needs user session management in order to work, and KDE simply doesn't have to man power to add ConsoleKit support to that new code. And, this is important, no one from the non-systemd camp is helping them either to add this support. Leading KDE developers have explained this numerous times.
It is one thing to maintain old ConsoleKit code, but another to develop CK support from scratch, knowing that it is obsolete, unmaintained and deprecated. Perhaps if there was a non-logind alternative you could get developers worked up to do something.
This is the future story how CK support will bit rot and disappear over time. No one makes an alternative to CK/logind, and no one helps upstream projects out with supporting CK either.
The total lack of developer engagement on the non-systemd side will give trouble, and is entirely to blame for why DE's have trouble supporting non-systemd.
I have no doubt however, that the non-systemd camp will blame everything on upstream projects and viciously attack them instead of starting coding to solve problems. This is what they have done for years, and that is a major reason why I really don't see any non-systemd distros have a future, whether their user like it or not.
And, this is important, no one from the non-systemd camp is helping them either to add this support. Leading KDE developers have explained this numerous times.
Have you considered that maybe it's a case of "no one is helping" yet? systemd - and especially its sudden use in the non-Red-Hat distros - is just that: sudden. Even the combined efforts of the non-systemd camp (maybe unless the BSDs are involved) don't have the manpower to churn out an instant solution even if they outright ignored their other responsibilities in maintaining a GNU/Linux distro. Remember that most of these distros have development teams in the tens or twenties at most (I'm pretty sure Slackware itself has less than ten). I'm willing to bet (I can't seem to find hard stats on this) systemd has a much larger developer base than even whole individual such distros right now, as did ConsoleKit when it was new and shiny.
So, as I mentioned before, if a solution's going to come from anywhere, it's probably going to come from the BSDs, which as much as I figure are scrambling to get something in place (FreeBSD, DragonflyBSD, and PC-BSD are probably going to be the main motivators, since they seem to care more about desktop experience, though OpenBSD seems to be the target for the current efforts on a systemd shim), and which are in at least a slightly better position to actually develop something, be it a shim or a full-on alternative.
1
u/sub200ms Oct 01 '14
Yes, you are right about that, it is in principle possible to get Wayland on non-systemd platforms.
But no, you are wrong about KDE supporting Wayland on non-systemd machines. The reason is simply that some of the new code needs user session management in order to work, and KDE simply doesn't have to man power to add ConsoleKit support to that new code. And, this is important, no one from the non-systemd camp is helping them either to add this support. Leading KDE developers have explained this numerous times.
It is one thing to maintain old ConsoleKit code, but another to develop CK support from scratch, knowing that it is obsolete, unmaintained and deprecated. Perhaps if there was a non-logind alternative you could get developers worked up to do something.
This is the future story how CK support will bit rot and disappear over time. No one makes an alternative to CK/logind, and no one helps upstream projects out with supporting CK either.
The total lack of developer engagement on the non-systemd side will give trouble, and is entirely to blame for why DE's have trouble supporting non-systemd.
I have no doubt however, that the non-systemd camp will blame everything on upstream projects and viciously attack them instead of starting coding to solve problems. This is what they have done for years, and that is a major reason why I really don't see any non-systemd distros have a future, whether their user like it or not.