I actually have realised that maybe the better approach would be to use 66 ( https://web.obarun.org/software/66/latest/). It's much easier to write services in 66 for me than s6 and it provides an easy and declarative way to do so which may be easier for folks coming from systemd. It's also based on 66 and supports execline as the default, so yeah. We are working towards 66 in alpine here: https://forum.obarun.org/d/1827-66-on-alpine-linux/41
My current job is precisely to make sure s6-rc gets integrated into Alpine and that there is an accessible UI for it. It would be nice if the work could avoid being duplicated, and if Alpine devs were faced with one unified proposal for multiple service managers rather than several independent and uncoordinated initiatives. So if you intend to make 66 an available service manager for Alpine, I suggest you coordinate with me to see what features 66 provides and how we can unify the interface as much as possible so that people can switch between 66, s6-rc and OpenRC as painlessly as possible. I'm not yet ready to work on the abstraction of the service manager engine (my estimate is that I'll start it in something like September or October): at the moment I'm working on a frontend for s6 commands. But if you are drafting a declarative syntax for services, I am interested in its design, so please keep me in the loop 🙂 -- Laurent
