s6

[mmdbalkhi]

Testing the changes

• I tested the changes in this PR: briefly

Local build testing

• I built this PR locally for my native architecture, X86_64(glibc)

---

• skalibs: update to 2.14.4.0.
• mdevd: update to 0.1.7.0.
• oblibs: update to 0.3.4.0.
• execline: update to 2.9.7.0.
• 66: update to 0.8.2.1.
• 66-tools: update to 0.1.2.0.
• s6: update to 2.13.2.0.
• s6-dns: update to 2.4.1.0.
• s6-linux-utils: update to 2.6.3.0.
• s6-networking: update to 2.7.1.0.
• s6-rc: update to 0.5.6.0.
• s6-man-pages: update to 2.13.1.0.1.
• s6-networking-man-pages: update to 2.7.0.4.1.
• s6-portable-utils: update to 2.3.1.0.
• s6-portable-utils-man-pages: update to 2.3.0.4.1.
• New package: s6-linux-init-man-pages-1.1.2.0.1
• New package: s6-linux-init-1.1.3.0

[leahneukirchen]

@mobinmob is this ok to merge?

[mobinmob]

@mobinmob is this ok to merge?

I am afk, seems fine. I will be able to test tommorow.
People that use 66 with my unofficial services should be aware that they are not compatible with the new 66 version. That is however not an issue with the distribution.

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

[jpnt]

Once this gets merged it would awesome to also have s6-frontend (https://git.skarnet.org/cgi-bin/cgit.cgi/s6-frontend/). It provides a higher-level interface for the s6 components, similar in intent to 66 but maintained directly by skarnet. Offline working sets and repository model make it especially useful for distributions (https://git.skarnet.org/software/s6-frontend/overview.html).

Opinion: Working with s6/s6-rc "raw" is digital pain. But I also do not want to use 66 because it does not feel as Unix-like as runit. 66 feels more like dinit or systemd, which is not bad, just preferences.

Including s6-frontend would give Void users another way to work with s6, without forcing anything on the system. I think it fits well with the flexibility of Void Linux, we have multiple libc options, multiple architectures/platforms, multiple initramfs generators, multiple bootloaders and now multiple init systems.

I will be testing this since it is not as straightforward as it sounds, I just wanted to put it out there.

[leahneukirchen]

Packaging s6-frontend is welcome.

@mmdbalkhi please rebase, then we can merge.

[jpnt]

s6-frontend requires yet another update of these packages in order to work (https://git.skarnet.org/cgi-bin/cgit.cgi/s6-frontend/tree/INSTALL).

I will be trying this stuff out eventually but man its so boring to update all this stuff manually. Do we have something like dependabot/renovate in void-packages? If automation sounds interesting hit me up.

[leahneukirchen]

Updating is fairly simple, you just need to run update-check to get the new versions, and then recompute hashes with xgensum -i.

Else you can try https://github.com/Piraty/xxtools/blob/master/xxautobump

[mmdbalkhi]

@jpnt s6-frontend 0.0.1.2 was added in #61224 Thanks for the suggestion