Hi !

>
> Something like
>
> cat<<EOF > /etc/dpkg/dpkg.cfg.d/exclude-systemd.cfg
> /etc/systemd/*
> /lib/systemd/*
> /usr/lib/systemd/*
> /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.

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

> and removing the content in those directories *looks* quite OK on
> *my* laptop (running Daedalus). No, I didn't test that.
>
> Use
>
> sudo find / -type d -name '*systemd*'
> sudo find / ! -type d -name '*systemd*'
>
> for lists of directories and non-directories to get an idea what
> you might want to zap. Check the content of the directories with
> something like
>
> sudo find / -type d -name '*systemd*' | xargs find
>
> Use dpkg's path-include to keep things that would otherwise be removed
> by a path-exclude (similar to git ignore's !).
>
> Hope that clarifies,
> --
> Olaf Meeuwissen
> _______________________________________________
> Dng mailing list
> Dng@???
> Manage your subscription: https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> Archive: https://lists.dyne.org/lurker/list/dng.en.html