Le 29/04/23 à 15:37, Faulk Johnny a écrit :
I am not saying to remove the systemd dependency. I am saying that
changing "systemd," to "systemd | elogind" under the control section
for the plymouth package in particular, NOT the build dependencies,
thus allowing installation on (and forcing a dependency on) either one
of them. Those who use a no-systemd system know full well there is a
risk, seeing as it's a pretty deliberate act to begin with in Debian.
Changing it as described above would have no affect at all on systemd
systems, as it would still pull in systemd and enforce that need.
Please reconsider this course of action.
The fact that plymouth package is depending on systemd has nothing to do
with the fact that it requires (e)logind (it actually doesn't, plymouth
runs at early boot and has nothing to do with a user session).
As said the dependency is needed because plymouth requires some udev
rules (namely /usr/lib/udev/rules.d/71-seat.rules) and tags to properly
detect the framebuffer/drm devices.
So as long at the rules file is shipped, in systemd package, plymouth
will have that dependency.
On Sat, Apr 29, 2023 at 6:25 AM, Laurent Bigonville
<bi...@debian.org>
Like explained in bug #1035076, the fact that systemd is pulled by
the
plymouth package doesn't mean you cannot use it with an other
initsystem
on debian, the package that actually changes the default
initsystem is
"systemd-sysv", not "systemd"
Removing the dependency might break plymouth at it requires some udev
rules files that are shipped by the systemd package (the rules are
used
to tag the framebuffer devices/heads installed on the machines).
So removing that could break some setup
Kind regards,
Laurent Bigonville
