On 2016-05-12 14:56:38 +0200, Andreas Henriksson wrote: > bootlogd conflicting with systemd-sysv isn't sufficient since people can > boot with systemd even without having systemd-sysv installed.
And perhaps it would be even a bad idea, because people might have systemd-sysv installed but might want to temporarily use another init system (e.g. for testing or in case of systemd failure). So, I don't think a conflict is a good solution. It is better to update the description as I suggested in my previous mail. > Declaring a conflicts against systemd package would also not be right > since it's quite likely people will have that package installed even > when they're using another init system. and even when using System-V init, the systemd package is mandatory for GNOME users (but also for udisks2 and maybe other things). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)