Michael Biebl: > Am 04.05.2018 um 13:47 schrieb Michael Biebl: >> Dropping #TMPFILES# means, systemd-tmpfiles will act on all tmpfiles. >> This would be a bit like if upgrading rsyslog would restart all system >> services (including rsyslog). That doesn't feel right. >> So I don't think dropping #TMPFILES# is the right approach. > > [...] > > One valid use cases this touches though is, that overriding tmpfiles in > /etc/tmpfiles.d should be supported. I.e. if there is a > /usr/lib/tmpfiles.d/dbus.conf and an admin wants to tweak that by > shipping a /etc/tmpfiles.d/dbus.conf, I don't think the package should > override that. > Afaics, this could easily be fixed by only using the name of the .conf > file, not the full path, so dh_installsystemd/dh_installinit would have > to generate > systemd-tmpfiles --create dbus.conf > instead of > systemd-tmpfiles --create /usr/lib/tmpfiles.d/dbus.conf > > Felipe et al, what do you think? > > (CC pkg-systemd-maintainers to have more eyes on this) > > Michael >
Hi, After a short chat with Felipe yesterday, I have updated the debhelper tooling (in git master) to generate "systemd-tmpfiles --create dbus.conf" instead of "systemd-tmpfiles --create /usr/lib/tmpfiles.d/dbus.conf". This solves one half of the issue (namely that package provided tmpfiles configs could not be overridden at all). On the other part of the issue, I will follow Michael's recommendation of keeping #TMPFILES# in the postinst. As I understand it, this effectively makes that part "wontfix". Thanks, ~Niels
