On 19 October 2012 21:06, Jan de Groot
Please don't. Consolekit is not maintained upstream anymore and should get killed with fire. null
I see no problem in maintaining ConsoleKit in [community] as long as
it doesn't cause any problems. The main reason why I'd like to keep
ConsoleKit in community is because the kdebase-workspace, which
requires ConsoleKit on systems using initscripts, takes relatively
long time to compile. If some serious issue arise I won't object to
moving it to AUR.
But if you are against ConsoleKit in [community], I can keep the
consolekit-related stuff in AUR, while maintaining initscripts in
[community] (although in fact initscripts without consolekit are
nearly worthless for me – I depend on KDE's NetworkManager applet).
On 20 October 2012 00:16, Dave Reisner
Package stats is purely aggregate. There is no such thing as tracking of users or machines, so anyone who's reported and uninstalled initscripts since, and then reported again isn't going to have the "desired" effect. Sadly, in its current state, there's very little stats in package stats.
d
Thanks for clarification. Lukas