How to handle tmpfiles.d in non-systemd environments

[Robie Basak]

On Tue, Feb 18, 2020 at 10:31:40AM +1300, Michael Hudson-Doyle wrote:
> On the face of it, the package is buggy. tmpfiles configs are processed by
> systemd, the package depends on the tmpfiles config being processed -> it
> should Depend: on systemd. This is not a path forward to having it work in
> a docker container though.

This is a good point. I believe this has been discussed in Debian, and
that there was an argument that it's better not to enforce that via a
dependency for now since doing so would preclude alternative init
systems from being usable. I don't know if that discussion concluded.

For Ubuntu specifically, I believe it's not buggy because we can assume
that systemd is present.

As you said though, this is largely unrelated to the Docker use case we
want to enable.

I commented in the bug about that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20200218/63ae4faf/attachment.sig>