| 1 |
On Thu, Nov 26, 2020 at 07:55:33AM +0100, Piotr Karbowski wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> On 25/11/2020 22.57, Georgy Yakovlev wrote: |
| 5 |
> > systemd-tmpfiles does not depend on any systemd-isms, does not need dbus, |
| 6 |
> > and is just a drop-in replacement, the only step needed is to emerge the |
| 7 |
> > package. |
| 8 |
> > it's a simple single binary + manpage, binary links to libacl and couple other |
| 9 |
> > system libs. |
| 10 |
> |
| 11 |
> Can confirm that systemd-tmpfiles works fine on OpenRC systems. Been |
| 12 |
> using it since end of October. |
| 13 |
> |
| 14 |
> Two things that are different in terms of interface to opentmpfiles is |
| 15 |
> that systemd-tmpfiles does not have --dry-run runtime option, and it |
| 16 |
> will complain if any /usr/lib/tmpfiles.d/*.conf uses /var/run instead of |
| 17 |
> /run, but that's just an warning. |
| 18 |
|
| 19 |
Also, have we tested this on musl systems? |
| 20 |
|
| 21 |
My plan is to take the tmpfiles code from systemd, like eudev and elogin |
| 22 |
have done, and rewrite it to not use the systemd libraries so it will be |
| 23 |
more portable. |
| 24 |
|
| 25 |
Once this happens, I'll probably switch the provider back to |
| 26 |
opentmpfiles. |
| 27 |
|
| 28 |
William |
Archives