s6-rc を Homebrew, apk でインストール

プロジェクトリンク

• ホームページ
• パッケージマネージャページ

コマンドとエイリアス

• s6-rc
• s6-rc-compile
• s6-rc-db
• s6-rc-dryrun
• s6-rc-format-upgrade
• s6-rc-init
• s6-rc-repo-init
• s6-rc-repo-list
• s6-rc-repo-sync
• s6-rc-set-change
• s6-rc-set-commit
• s6-rc-set-copy
• s6-rc-set-delete
• s6-rc-set-fix
• s6-rc-set-install
• s6-rc-set-new
• s6-rc-set-status
• s6-rc-update

プロジェクトの歴史

s6-rc was created as the dependency-aware service-management layer for s6 systems. It manages both supervised long-running services and one-time state transitions, plus bundles that name groups of atomic services.

An initially planned 1.0.0.0 design proved too ambitious and was scaled back in favor of incremental development. Starting with 0.6.0.0, the suite added repository and set-management tools intended to help users and distributions organize source definitions and compiled service databases.

採用の歴史

s6-rc serves systems built around the s6 supervision infrastructure and is packaged by Homebrew and Alpine according to source_facts.package-manager. Its documentation explicitly addresses distribution package upgrades: packages may ship service definitions, after which administrators compile and live-update the database.

使われ方

Administrators write directories describing longruns, oneshots, and bundles, compile them with `s6-rc-compile`, initialize live state with `s6-rc-init`, and request transitions with `s6-rc change`. `s6-rc-update` replaces a live compiled database without rebooting. Locations for source definitions, compiled databases, and live state are deployment choices or build-time defaults rather than one universal configuration file.

パッケージ好きにとっての重要性

s6-rc is notable for separating declarative service definitions and offline dependency-graph compilation from online state changes. This architecture makes database formats, upgrade tooling, dependency closure, and package-supplied service definitions central concerns—precisely the details that interest init-system and distribution maintainers.

タイムライン

• 0.6.0.0: Repository and set-management commands were introduced for organizing service-definition sources and compiled databases.
• 0.7.0.0: Added reload support and changed the compiled database format.

Related projects

• s6 supplies the underlying supervision tree. skalibs and execline are required dependencies. The official site names anopa and nosh as comparable service-management work and recommends s6-frontend as a higher-level entry point.

ソース

• https://www.skarnet.org/software/s6-rc/
• https://www.skarnet.org/software/s6-rc/overview.html
• https://www.skarnet.org/software/s6-rc/upgrade.html
• source_facts.package-manager