Skip to main content ↑ ↓
Topic: Best practice for packaging software that depends on systemd-only features? (Read 632 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Best practice for packaging software that depends on systemd-only features?

Hey fellow Artix devs,

I’m working on a small CLI tool that relies on some features usually tied to systemd (specifically journald and timers). I’d like to package it for Artix and make it more init-agnostic.

Has anyone here dealt with converting systemd-tied software into something that works smoothly with OpenRC or Runit?

I'm considering using cronie for timers and syslog-ng or plain file logging instead of journald. But curious if there’s a clean pattern or wrapper that’s preferred within the Artix packaging philosophy.

Appreciate any thoughts or advice!

— Jhonn Mick
 

Re: Best practice for packaging software that depends on systemd-only features?

Reply #1 –
The UNIX way, easy:
systemd-timers -> cron
logging: syslog(3) and let the local logger catch the messages