On Wed, Jan 25, 2012 at 11:31 AM, Lennart Poettering <[email protected]> wrote:
> > I figure that means that we probably have to keep code for CK compat in > GNOME, if CK matters. My own patches for GNOME stuff and otherwise are > actually written in a way that systemd and CK are detected at runtime, > thus allowing distros like Debian to ship a single version of the > software that's compatible with CK and systemd at the same time. But > others have not been as careful as I was and have this as a compile time > switch only. > > And running partly CK software and partly systemd software side-by-side > is as mentioned a bad idea. This breaks at many places, for example with > PK authorizations (and you totally lost with genuine systemd features > anyway, such as true automatic multi-seat). > > Sorry if this is disappointing, > > Lennart The CK replacement patches I have contributed are mostly configure-time switchable between CK and systemd (on the theory that an OS can really only have one init system...). However, vuntz made me rewrite the gnome-session patch to do runtime detection. And it should not be hard to add runtime detection to the other places; but I don't really consider it a good use of my time, and I'd hope that the distributions that want to support choose-your-own-init-system would step up and work on this. I don't think we need to set a short sunset deadline for ConsoleKit support, but we should communicate that distributors who need ConsoleKit (because they are not using Linux, or are not willing to use systemd) may want to consider becoming active in ensuring that it stays alive. _______________________________________________ [email protected] http://mail.gnome.org/mailman/listinfo/release-team Release-team lurker? Do NOT participate in discussions.
