On Tue, Nov 15, 2016 at 10:49 AM, Dustin C. Hatch <admiraln...@gmail.com> wrote: > On 2016-11-14 23:09, Michał Górny wrote: >> On Mon, 14 Nov 2016 18:23:10 -0600 >> William Hubbs <willi...@gentoo.org> wrote: >> >>> Hi all, >>> >>> I have been working on splitting the tmpfiles functionality out of >>> OpenRC [1], and I believe the new package is about to enter the tree. >>> >>> OpenRC itself doesn't need this package to boot since it doesn't use >>> tmpfiles.d files, but other software does need it. >>> >>> This brings up a couple of questions. >>> >>> Since we now will have two different ways to process tmpfiles, is >>> virtual/tmpfiles appropriate, with the default being opentmpfiles? >> >> Yes. Virtual will allow us to control list of supported implementations >> easily. We can also use it to control different versions of tmpfiles >> format. >> >>> Once opentmpfiles is in the tree and stable, should virtual/tmpfiles >>> be added to @system, or should we have the packages that need it rdepend >>> on it directly? I tend to lean toward the second option. >> >> We will RDEPEND on it via tmpfiles.eclass. I think floppym has a draft >> somewhere. In case that draft uses DEPEND, it just occurred to me that >> we need RDEPEND for pkg_postinst(). >> > > What about administrator-specified temporary files in /etc/tmpfiles.d? > It would be rather unfortunate to have stuff suddenly stop working > because an OpenRC got updated and stopped creating these temporary files. >
Does it create them today? I thought this was a new feature addition. If it does then news should cover that situation, and the admin can just add either the virtual or the preferred implementation to their @world. -- Rich
