On Fri, Oct 19, 2012 at 12:17 PM, Lukas Jirkovsky <l.jirkovsky@gmail.com> wrote:
I'd like to maintain some basic support support for consolekit in [community], more specifically the polkit-consolekit, kdebase-workspace-consolekit packages and eventually consolekit package itself as long as possible, if you're not against it.
I'm running kde (networkmanager) without systemd without problems on my laptop with these packages.
For what it is worth (not much, as I don't have any say over what goes on in [community]), I think this is not really a good idea. Wanting to keep initscripts around I would support, but doing this for consolekit seems like a bad idea (at least in official repositories). CK is dead upstream and has always had various issues, that I'd like to be able to forget about soon. Also, I would have thought that whatever people had against systemd, they would also have against CK? I.e., I assumed people would only want to stick with initscripts if they were running some minimalist system without dbus/polkit/networkmanager/... . That said, if you really do want to keep using CK, then I suggest it should be done in one of two ways: 1) put the required packages in a third-party repo/AUR so people understand that it is not really supported 2) keep support for CK enabled in the packages where this is possible (kde is one I believe) and only add the ones where you have to make a compile-time choice to community (consolekit,polkit-consolekit,networkmanager-consolekit). Just my two cents, -t