On 09/02/19 23:46, Mark Hindley wrote:
> On Sat, Feb 09, 2019 at 09:08:52AM +1300, Daniel Reurich wrote:
>> On 09/02/19 03:04, Mark Hindley wrote:
>>> On Fri, Feb 08, 2019 at 06:53:46AM +0000, Mark Hindley wrote:
>>>> On Fri, Feb 08, 2019 at 10:33:06AM +1300, Daniel Reurich wrote:
>>>>>> How do we want to resolve this? With my elogind hat on, I would like to see slim
>>>>>> work with it. It isn't immediately clear to me that slim can be made to support
>>>>>> both elogind and consolekit in a single binary.
>>>>>
>>>>> I'm not sure on that as consolekit2 is supposed to also be able to
>>>>> utilise logind interfaces - but I don't know how mature that is yet.
>>>>
>>>> Thanks, I didn't realise that. I will have to do some reading as to how that is
>>>> supposed to work. At the moment elogind and consolkit conflict and are not
>>>> coinstallable.
>>>
>>> Dan,
>>>
>>> Can you point me to the documentation for this?
>>
>> "use the source, Luke" ;-)
>>>
>>> I can only find mention of consolekit2 emulating the logind implementation. But
>>> it uses its own DBus API.
>>>
>> https://consolekit2.github.io/ConsoleKit2/
>
> Yes that is what I found. I can't see anything about consolekit2 utilising
> logind interfaces there. It emulates some logind methods but on a
> differen DBUs API. Am I missing something?
>

I must've been mistaken then. So consolekit2 attempts to present a
logind like interface for those desktops that abandoned logind.

Ok that's no big deal I don't think.

I'd suggest making slim depend on consolekit2 and build it.

If your onto it now, go for it. Otherwise I might do it in the next day
or so as I need it in ceres for an install I'm doing.

Cheers,
    Daniel

--
Daniel Reurich
Centurion Computer Technology (2005) Ltd.
021 797 722