Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

[Laurent Bigonville]

On 20/09/19 11:16, Mark Hindley wrote:
> On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote:
> [...]
>> Bottom line, is libelogind even needed in the archive to achieve your goal
>> of having an implementation of the login1 D-Bus API not requiring systemd as
>> PID1?
> Thanks.
>
> I think you are correct that the login1 DBus API doesn't require libsystemd0 or
> libelogind0. However some packages, notably policykit use the sd-login(3) API
> which is part of libsystemd0 or libelogind0. Whilst the APIs, and symbol ABIs
> are the same between the two libraries (with the caveats noted in the
> libelogind0 package description) the implementations differ. I have been tolkd
> int he past by elogind upstream that it is not possible for elogind to use
> libsystemd0. For example libsystemd0 requires the concept of slices which
> elogind doesn't have.
>
> The only way I have got all of these components to work together on an elogind
> systemd is to ensure everything uses libelogind0.

Can't this be stubbed or mocked on the elogind side?