Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-05 Thread Simon McVittie
On Mon, 05 Jun 2023 at 01:36:25 +0100, Luca Boccassi wrote: > If it is useful, adding a "default-tmpfiles" or so virtual package > would be fine by me - but with the kfreebsd port being retired soon, > and i386 (for hurd) going the way of the dodo, I'm not sure it would > be very useful? I don't th

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-05 Thread Simon McVittie
On Mon, 05 Jun 2023 at 01:36:25 +0100, Luca Boccassi wrote: > On Sun, 4 Jun 2023 at 14:56, Simon McVittie wrote: > > So I think the only realistic options for packages that hard-require > > this functionality (not all do) are: > > > > 1. Depends: systemd | systemd-tmpfiles > > 2. Depends: systemd-

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-05 Thread Luca Boccassi
On Mon, 5 Jun 2023 10:11:46 +0100 Simon McVittie wrote: > On Mon, 05 Jun 2023 at 01:36:25 +0100, Luca Boccassi wrote: > > Our time is worth more than 80K or whatever it is of disk space in a > > throw-away container. > > I agree that the systemd maintainers' time is a limited resource that we > s

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-05 Thread Luca Boccassi
On Mon, 5 Jun 2023 09:53:39 +0100 Simon McVittie wrote: > On Mon, 05 Jun 2023 at 01:36:25 +0100, Luca Boccassi wrote: > > If it is useful, adding a "default-tmpfiles" or so virtual package > > would be fine by me - but with the kfreebsd port being retired soon, > > and i386 (for hurd) going the wa

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-05 Thread Helmut Grohne
On Sun, Jun 04, 2023 at 02:56:59PM +0100, Simon McVittie wrote: > I think one way or another, if anyone is going to set a package-level > dependency on systemd-tmpfiles, the first (preferred) dependency needs to > be on either a concrete provider (systemd or systemd-tmpfiles-standalone > in this ca