From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/3] tmpfiles.eclass: Support using on non-Linux systems
Date: Tue, 02 May 2017 16:56:39 +0200 [thread overview]
Message-ID: <1493736999.1420.1.camel@gentoo.org> (raw)
In-Reply-To: <20170502143842.GA22289@linux1>
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]
On wto, 2017-05-02 at 09:38 -0500, William Hubbs wrote:
> On Sun, Apr 30, 2017 at 09:06:53PM +0200, Michał Górny wrote:
> > Fix the eclass code to remove the misguided Linux conditionals.
> > The whole purpose of the eclass was to avoid having to implement
> > fallback logic for systems not having service manager tmpfiles.d
> > support. Making it conditional to Linux implied that for non-Linux
> > systems (Prefix, FreeBSD) we would have to implement explicit fallback
> > to create the necessary directories.
> >
> > While systemd (and therefore systemd-tmpfilesd) is indeed
> > Linux-specific, the opentmpfiles implementation should be pretty
> > portable and there is no reason to restrict it to Linux only, or to
> > prevent using it on non-Linux OpenRC (and non-OpenRC) systems.
>
> Opentmpfiles can run right now on non-openrc systems, but it requires a
> linux host; that is why the Linux conditionals are there. We currently support
> selinux and even more specific linux code is coming with the btrfs
> subvolume support.
It's funny because I've just got a confirmation that it works
on FreeBSD.
> The purpose of opentmpfiles is to provide a non-systemd program that
> mirrors the behavior of systemd-tmpfiles so that Linux users do not have
> to install systemd, but there are features that definitely would not
> work on other hosts.
We need a tool that works for everyone. Not excuses not to support Linux
just because systemd does not.
> Also, the tmpfiles.d standard doesn't allow tmpfiles to do things based
> on operating systems,
And what's the problem with installing tmpfiles.d files aligned to
the operating system in question? After all, you don't tell everyone not
to use OpenRC outside Linux just because someone might have put Linux-
specific paths in the init.d file.
> and the configuration search paths (particularly
> /run/tmpfiles.d and the non-support of /lib/tmpfiles.d) are linux specific.
>
Does that hurt anyone? We're talking about Gentoo/FBSD and Gentoo
Prefix, i.e. Gentoo-flavored systems which we have control over. If you
really insist, I can ask our FBSD/Prefix teams to look through the code
and make sure that it works across all interesting platforms.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-05-02 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 19:06 [gentoo-dev] [PATCH 1/3] tmpfiles.eclass: Support using on non-Linux systems Michał Górny
2017-04-30 19:06 ` [gentoo-dev] [PATCH 2/3] tmpfiles.eclass: Explicit warn on ROOT != / to avoid breakage Michał Górny
2017-04-30 19:06 ` [gentoo-dev] [PATCH 3/3] app-portage/eix: Convert to tmpfiles.eclass (example) Michał Górny
2017-05-02 14:38 ` [gentoo-dev] [PATCH 1/3] tmpfiles.eclass: Support using on non-Linux systems William Hubbs
2017-05-02 14:56 ` Michał Górny [this message]
2017-05-02 16:21 ` 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=1493736999.1420.1.camel@gentoo.org \
--to=mgorny@gentoo.org \
--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