Dimitry, On Thu, May 07, 2020 at 09:52:18AM +0100, Mark Hindley wrote: > However, that does not help in this case. elogind has to conflict with systemd > as they include some duplicate files. I have to admit to being less convinced > by > the systemctl Provides: systemd. I understand the idea behind it, but systemd > is > much (much, much!) more than systemctl(1). Wouldn't having systemctl > Conflicts: > and Replaces: systemd be sufficient? AFAICS, that would restore the > coinstallability with elogind and resolve #959828?
I have just found #959174 and now understand more fully your motivation for adding Provides: systemd to systemctl. I sympathise and have come across a number of similar (unresolved) situations -- see #935304 for example. And the common systemd-tmpfiles/opentmpfiles interface remains unresolved in #952897. Best wishes Mark
