1 |
On wto, 2017-05-02 at 09:38 -0500, William Hubbs wrote: |
2 |
> On Sun, Apr 30, 2017 at 09:06:53PM +0200, Michał Górny wrote: |
3 |
> > Fix the eclass code to remove the misguided Linux conditionals. |
4 |
> > The whole purpose of the eclass was to avoid having to implement |
5 |
> > fallback logic for systems not having service manager tmpfiles.d |
6 |
> > support. Making it conditional to Linux implied that for non-Linux |
7 |
> > systems (Prefix, FreeBSD) we would have to implement explicit fallback |
8 |
> > to create the necessary directories. |
9 |
> > |
10 |
> > While systemd (and therefore systemd-tmpfilesd) is indeed |
11 |
> > Linux-specific, the opentmpfiles implementation should be pretty |
12 |
> > portable and there is no reason to restrict it to Linux only, or to |
13 |
> > prevent using it on non-Linux OpenRC (and non-OpenRC) systems. |
14 |
> |
15 |
> Opentmpfiles can run right now on non-openrc systems, but it requires a |
16 |
> linux host; that is why the Linux conditionals are there. We currently support |
17 |
> selinux and even more specific linux code is coming with the btrfs |
18 |
> subvolume support. |
19 |
|
20 |
It's funny because I've just got a confirmation that it works |
21 |
on FreeBSD. |
22 |
|
23 |
> The purpose of opentmpfiles is to provide a non-systemd program that |
24 |
> mirrors the behavior of systemd-tmpfiles so that Linux users do not have |
25 |
> to install systemd, but there are features that definitely would not |
26 |
> work on other hosts. |
27 |
|
28 |
We need a tool that works for everyone. Not excuses not to support Linux |
29 |
just because systemd does not. |
30 |
|
31 |
> Also, the tmpfiles.d standard doesn't allow tmpfiles to do things based |
32 |
> on operating systems, |
33 |
|
34 |
And what's the problem with installing tmpfiles.d files aligned to |
35 |
the operating system in question? After all, you don't tell everyone not |
36 |
to use OpenRC outside Linux just because someone might have put Linux- |
37 |
specific paths in the init.d file. |
38 |
|
39 |
> and the configuration search paths (particularly |
40 |
> /run/tmpfiles.d and the non-support of /lib/tmpfiles.d) are linux specific. |
41 |
> |
42 |
|
43 |
Does that hurt anyone? We're talking about Gentoo/FBSD and Gentoo |
44 |
Prefix, i.e. Gentoo-flavored systems which we have control over. If you |
45 |
really insist, I can ask our FBSD/Prefix teams to look through the code |
46 |
and make sure that it works across all interesting platforms. |
47 |
|
48 |
-- |
49 |
Best regards, |
50 |
Michał Górny |