[arch-dev-public] consolekit dependencies? - Arch-dev-public - lists.archlinux.org

newer
[arch-dev-public] Signoff report...

[arch-dev-public] consolekit dependencies?

older
[arch-dev-public] Services on...

Thomas Bächler

13 Oct 2012 13 Oct '12

9:42 a.m.

Most (all?) of our login manager still depend on consolekit. However, since consolekit support will be stripped from polkit when gnome-unstable goes to testing (soon?), registering consolekit sessions on login has no effect whatsoever. Should we rebuild our login managers to remove the consolekit dependencies? I rebuilt kdebase-workspace locally yesterday, and polkit seems to work just fine. kde itself does not use consolekit, except through polkit.

Attachments:

signature.asc (application/pgp-signature — 897 bytes)

Show replies by thread

Sébastien Luttringer

13 Oct 13 Oct

12:19 p.m.

On Sat, Oct 13, 2012 at 11:42 AM, Thomas Bächler wrote:

Most (all?) of our login manager still depend on consolekit. However, since consolekit support will be stripped from polkit when gnome-unstable goes to testing (soon?), registering consolekit sessions on login has no effect whatsoever.

Should we rebuild our login managers to remove the consolekit dependencies?

I rebuilt kdebase-workspace locally yesterday, and polkit seems to work just fine. kde itself does not use consolekit, except through polkit.

Tom build a version 0.107[1][2] of polkit which works fine with systemd. [1] https://dev.archlinux.org/~tomegun/ [2] https://mailman.archlinux.org/pipermail/arch-general/2012-August/029344.html Cheers, -- Sébastien "Seblu" Luttringer https://www.seblu.net GPG: 0x2072D77A

Andrea Scarpino

1:14 p.m.

On Saturday 13 October 2012 11:42:41 Thomas Bächler wrote:

Most (all?) of our login manager still depend on consolekit. However, since consolekit support will be stripped from polkit when gnome-unstable goes to testing (soon?), registering consolekit sessions on login has no effect whatsoever.

Should we rebuild our login managers to remove the consolekit dependencies?

I rebuilt kdebase-workspace locally yesterday, and polkit seems to work just fine. kde itself does not use consolekit, except through polkit.

It's ok for me. +1 to remove CK. PS. NetworkManager users will need nm 0.9.6.0-3 from gnome-unstable; it will be moved together with gnome, so this isn't a stopper. -- Andrea

Andrea Scarpino

2:30 p.m.

On Saturday 13 October 2012 14:19:56 Sébastien Luttringer wrote:

Tom build a version 0.107[1][2] of polkit which works fine with systemd.

AFAIK this is the same polkit we have in [testing] right now. -- Andrea

Tom Gundersen

2:34 p.m.

On Sat, Oct 13, 2012 at 11:42 AM, Thomas Bächler wrote:

Most (all?) of our login manager still depend on consolekit. However, since consolekit support will be stripped from polkit when gnome-unstable goes to testing (soon?), registering consolekit sessions on login has no effect whatsoever.

Should we rebuild our login managers to remove the consolekit dependencies?

I rebuilt kdebase-workspace locally yesterday, and polkit seems to work just fine. kde itself does not use consolekit, except through polkit.

Doing this makes sense to me. However, to make things clear-cut, it would be best if we could entirely remove consolekit from our repos and put up an announcement. That way people will not be confused as to why things stop working if they are not using logind. In addition to the gnome+kde packages the relevant packages we would have to make sure still work without consolekit are: lxdm oblogout slim udiskie (optional) xfce4-session xorg-xdm Cheers, Tom

Tom Gundersen

2:37 p.m.

On Sat, Oct 13, 2012 at 4:30 PM, Andrea Scarpino wrote:

On Saturday 13 October 2012 14:19:56 Sébastien Luttringer wrote:

...
Tom build a version 0.107[1][2] of polkit which works fine with systemd.

AFAIK this is the same polkit we have in [testing] right now.

The version I built had a custom patch to enable CK or systemd to be chosen at run-time. It was rejected upstream and I think it was removed from our package. I think it would make the most sense to just get rid of CK as mention in my previous email rather than try to make this work downstream. -t

Andrea Scarpino

2:44 p.m.

On Saturday 13 October 2012 16:34:04 Tom Gundersen wrote:

Doing this makes sense to me. However, to make things clear-cut, it would be best if we could entirely remove consolekit from our repos and put up an announcement. That way people will not be confused as to why things stop working if they are not using logind.

In addition to the gnome+kde packages the relevant packages we would have to make sure still work without consolekit are:

lxdm oblogout slim udiskie (optional) xfce4-session xorg-xdm

TODO list started at https://www.archlinux.org/todo/188/ -- Andrea

Thomas Bächler

2:45 p.m.

Am 13.10.2012 16:34, schrieb Tom Gundersen:

On Sat, Oct 13, 2012 at 11:42 AM, Thomas Bächler wrote:

...
Most (all?) of our login manager still depend on consolekit. However, since consolekit support will be stripped from polkit when gnome-unstable goes to testing (soon?), registering consolekit sessions on login has no effect whatsoever.

Should we rebuild our login managers to remove the consolekit dependencies?

I rebuilt kdebase-workspace locally yesterday, and polkit seems to work just fine. kde itself does not use consolekit, except through polkit.

Doing this makes sense to me. However, to make things clear-cut, it would be best if we could entirely remove consolekit from our repos and put up an announcement. That way people will not be confused as to why things stop working if they are not using logind.

In addition to the gnome+kde packages the relevant packages we would have to make sure still work without consolekit are:

lxdm oblogout slim udiskie (optional) xfce4-session xorg-xdm

Agreed, we need to make this all at once. I think Andrea is starting a TODO list.

4231

Age (days ago)

4231

Last active (days ago)

Download

7 comments

4 participants

tags

participants (4)

Andrea Scarpino
Sébastien Luttringer
Thomas Bächler
Tom Gundersen