Hi,

Lorenz via Dng <dng@???> writes:

> Hi !
>
>> Something like
>>
>> cat<<EOF > /etc/dpkg/dpkg.cfg.d/exclude-systemd.cfg
>> /etc/systemd/*
>> /lib/systemd/*
>> /usr/lib/systemd/*
>> /var/lib/systemd/*
>> EOF

Correction! The above should have been

cat<<EOF > /etc/dpkg/dpkg.cfg.d/exclude-systemd.cfg
path-exclude=/etc/systemd/*
path-exclude=/lib/systemd/*
path-exclude=/usr/lib/systemd/*
path-exclude=/var/lib/systemd/*
EOF

> Systemd services files (stuff in /usr/lib/systemd/*) may be used by
> other packages for heuristics, so if someone is going to test this I
> suggest to pay attention to the fact that other packages may
> malfunction subtly.

Thanks for the heads up!

I might give it a go sometime but it feels a bit like trying to get rid
of, e.g. bash completion files because you are using zsh.

It's not like the systemd cruft takes up a lot of space. On my Daedalus
box it's less than half of a MB, with most of it in /var/lib/systemd/.
Oops, that actually seems to be for deb-systemd-helper, which comes in
init-system-helpers. According to the deb-systemd-helper manual page

deb-systemd-helper - subset of systemctl for machines not running systemd

so you probably want to keep those ... with something like

cat <<EOF >> /etc/dpkg/dpkg.cfg.d/include-systemd.cfg
path-include=/var/lib/systemd/deb-systemd-helper-*
path-include=/var/lib/systemd/deb-systemd-user-helper-*
EOF

where I am *guessing* that deb-systemd-helper moves files around based
on maintainer scripts using enable, disable and what not.
You're not supposed to use it yourself, apparently.

> For example, early version of runit-services package used to test for
> systemd and sysv services files to detect whether the equivalent runit
> service should be deployed on the system. The current version of
> runit-services no longer rely on systemd files [1] but other catch-all
> packages like orphan-sysvinit-scripts may still do that.
>
> Best,
> Lorenzo
>
> [1] now it looks for the bin path which is far more robust

--
Olaf Meeuwissen