66 is an excellent service management suite which uses s6 under the hood, provides a simple declarative INI format for services, manages dependency without races, handles logging with s6-log such that logs from different services stay separate, and makes sure that no line of logs is lost in the event of an error [text format, fd-holding etc... to achieve that].
The main `sys-apps/66`, a set of auxillary tools `sys-apps/66-tools` and the underlying convenience library `sys-libs/oblibs` has been PR'd for the gentoo repo, and will soon be temporarily available via a separate overlay. The PR: https://github.com/gentoo/gentoo/pull/41402 The required bootscripts etc... aren't yet packaged, and will be available soon. The person packaging and doing the PR is myself, and I have ZERO experience beforehand, and sorry, it's causing some minor issues. [Should I depend on dbus-broker[-launcher] when the 66-tools provides an alternative launcher by USE=dbus? OR should I let the users do it via `elog`? OR should I use some other useflag other than "dbus"?] [I've decided to go with the elog approach; might also choose to disable the dbus part completely... if even that fails] [What's the proxy-maint thing that the QAreport complains? Plz, IDK what it is.] Why can't I use "${PV}" "${PN}" in the HOMEPAGE= ? Without those variables in there I'd have to update them on *every* version upgrade.
