| 1 |
On Sun, Apr 30, 2017 at 09:06:53PM +0200, Michał Górny wrote: |
| 2 |
> Fix the eclass code to remove the misguided Linux conditionals. |
| 3 |
> The whole purpose of the eclass was to avoid having to implement |
| 4 |
> fallback logic for systems not having service manager tmpfiles.d |
| 5 |
> support. Making it conditional to Linux implied that for non-Linux |
| 6 |
> systems (Prefix, FreeBSD) we would have to implement explicit fallback |
| 7 |
> to create the necessary directories. |
| 8 |
> |
| 9 |
> While systemd (and therefore systemd-tmpfilesd) is indeed |
| 10 |
> Linux-specific, the opentmpfiles implementation should be pretty |
| 11 |
> portable and there is no reason to restrict it to Linux only, or to |
| 12 |
> prevent using it on non-Linux OpenRC (and non-OpenRC) systems. |
| 13 |
|
| 14 |
Opentmpfiles can run right now on non-openrc systems, but it requires a |
| 15 |
linux host; that is why the Linux conditionals are there. We currently support |
| 16 |
selinux and even more specific linux code is coming with the btrfs |
| 17 |
subvolume support. |
| 18 |
|
| 19 |
The purpose of opentmpfiles is to provide a non-systemd program that |
| 20 |
mirrors the behavior of systemd-tmpfiles so that Linux users do not have |
| 21 |
to install systemd, but there are features that definitely would not |
| 22 |
work on other hosts. |
| 23 |
|
| 24 |
Also, the tmpfiles.d standard doesn't allow tmpfiles to do things based |
| 25 |
on operating systems, and the configuration search paths (particularly |
| 26 |
/run/tmpfiles.d and the non-support of /lib/tmpfiles.d) are linux specific. |
| 27 |
|
| 28 |
William |
Archives