On Fri, 2019-04-26 at 07:07 -0400, Michael Orlitzky wrote: > On 4/26/19 12:53 AM, Michał Górny wrote: > > > And the only reason we would need a transient directory created and/or > > > cleaned-up is because one of those service managers is going to start a > > > program that needs it. Two of them can use the tmpfiles mechanism, but > > > the others must handle it on their own: in particular, they don't need > > > tmpfiles_process() to do anything. > > > > > > > No. tmpfiles is also used for programs started directly by user, such > > as eix. > > > > Good example. Does eix work on a machine running something other than > systemd or OpenRC?
Yes, it does. > I don't think so -- not if it needs that tmpfiles > entry to be processed every reboot. Thus it should have its own RDEPEND > on virtual/tmpfiles, making the one in the eclass redundant. It doesn't need to be processed every reboot. It needs to be processed at least once. Now, if you were doing something fancy like having /var/cache on tmpfs, then it would need to be processed on reboot. > > I suspect the same is true of any other example. Let's get to the point: > is there a single example of a package that works with runit, sysvinit, > or daemontools but which needs tmpfiles_process() to run? The general assumption we made here is that if you use OpenRC or systemd, you may have fancy stuff like /tmp on tmpfs, and you want tmpfiles processing running every reboot. If you don't, we assume you need to run it at least once, to get the directories initialized. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
