From: "Dustin C. Hatch" <admiralnemo@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] tmpfiles virtual
Date: Tue, 15 Nov 2016 09:49:22 -0600 [thread overview]
Message-ID: <582B2E82.9000200@gmail.com> (raw)
In-Reply-To: <20161115060942.37458d8f.mgorny@gentoo.org>
On 2016-11-14 23:09, Michał Górny wrote:
> On Mon, 14 Nov 2016 18:23:10 -0600
> William Hubbs <williamh@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.
--
♫Dustin
next prev parent reply other threads:[~2016-11-15 15:49 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 0:23 [gentoo-dev] tmpfiles virtual William Hubbs
2016-11-15 5:09 ` Michał Górny
2016-11-15 15:49 ` Dustin C. Hatch [this message]
2016-11-15 16:50 ` Rich Freeman
2016-11-15 16:56 ` Michał Górny
2016-11-15 17:56 ` William Hubbs
2016-11-15 18:57 ` Ian Stakenvicius
2016-11-15 19:42 ` Michał Górny
2016-11-15 19:51 ` Ian Stakenvicius
2016-11-15 19:56 ` Mike Gilbert
2016-11-16 13:57 ` Ian Stakenvicius
2016-11-16 15:08 ` William Hubbs
2016-11-16 15:14 ` Ian Stakenvicius
2016-11-16 17:03 ` William Hubbs
2016-11-16 18:04 ` Ian Stakenvicius
2016-11-16 20:21 ` William Hubbs
2016-11-16 23:09 ` Ian Stakenvicius
2016-11-16 23:16 ` William Hubbs
2016-11-16 23:19 ` Ian Stakenvicius
2016-11-16 23:25 ` William Hubbs
2016-11-16 23:45 ` Ian Stakenvicius
2016-11-17 1:41 ` Rich Freeman
2016-11-17 2:19 ` Mike Gilbert
2016-11-17 4:16 ` Ian Stakenvicius
2016-11-17 21:58 ` [gentoo-dev] " Martin Vaeth
2016-11-18 0:41 ` Rich Freeman
2016-11-17 0:09 ` [gentoo-dev] " Mike Gilbert
2016-11-17 6:03 ` Michał Górny
2016-11-17 15:02 ` Ian Stakenvicius
2016-11-17 17:22 ` William Hubbs
2016-11-17 19:00 ` Ian Stakenvicius
2016-11-17 18:46 ` Michał Górny
2016-11-17 18:49 ` Michał Górny
2016-11-17 19:01 ` William Hubbs
2016-11-17 19:10 ` Ian Stakenvicius
2016-11-17 19:42 ` Michał Górny
2016-11-17 20:07 ` Ian Stakenvicius
2016-11-17 20:21 ` Rich Freeman
2016-11-17 21:38 ` [gentoo-dev] " Martin Vaeth
2016-11-17 20:50 ` [gentoo-dev] " Michał Górny
2016-11-17 22:19 ` Ian Stakenvicius
2016-11-15 17:11 ` Mike Gilbert
2016-11-15 18:22 ` William Hubbs
2016-11-15 19:40 ` Michał Górny
2016-11-18 18:42 ` William Hubbs
2016-11-18 18:46 ` Mike Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=582B2E82.9000200@gmail.com \
--to=admiralnemo@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox