Artix Linux Forum

Artix Linux => Software development => Topic started by: jhonnmick on 16 July 2025, 23:41:20

Title: Best practice for packaging software that depends on systemd-only features?
Post by: jhonnmick on 16 July 2025, 23:41:20
Hey fellow Artix devs,

I’m working on a small CLI tool (https://calculadoradedias.com/vividos/) 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
Title: Re: Best practice for packaging software that depends on systemd-only features?
Post by: nous on 17 July 2025, 19:33:08
The UNIX way, easy:
systemd-timers -> cron
logging: syslog(3) and let the local logger catch the messages