The skarnet.org service manager https://git.skarnet.org/cgit/s6-rc/atom/package/deps.mak?h=v0.8.0.0 2026-10-17T04:10:16Z 2026-10-17T04:10:16Z Laurent Bercot ska-skaware@skarnet.org 2026-10-17T04:10:16Z urn:sha1:6ada80ed7e45ed630e4d9877a9b11e2dfddb4758 Now that everything is in place, we go for the main thing: add snapshot support to s6-rc-set install. The workflow is: - check the major version of the old db against the current s6-rc - if the old db is up to date, nothing changes - otherwise: + find the snapshot corresponding to the old db + compile it + copy the snapshot db to the bootdir + call s6-rc-format-upgrade on it + atomically switch the bootdb to it. At this point the snapshot is the new bootdb: same as the old db, but with the correct major version. + unconditionally remove the old db + and now we can perform the regular s6-rc-update with the wanted set, since they have the same major. We also add --no-snapshot options to s6-rc-set-commit and s6-rc-set-install, and propagate them in the supporting functions, so users can manually skip all this bloat (and this is important for the initial install). All that remains is cleaning up obsolete snapshots. This will probably go at the end of s6-rc-set-install as well. 2026-10-09T00:59:02Z Laurent Bercot ska-skaware@skarnet.org 2026-10-09T00:59:02Z urn:sha1:c71344185cc93d9322513a1d9506cb14b1c308a2 2026-10-09T00:40:33Z Laurent Bercot ska-skaware@skarnet.org 2026-10-09T00:40:33Z urn:sha1:a6883e06261447cec639c6d260270ec0664c2153 2026-10-09T00:30:42Z Laurent Bercot ska-skaware@skarnet.org 2026-10-09T00:30:42Z urn:sha1:99ff79f0db04a70e46ac0f2717979ab25de75a78 2026-10-09T00:02:46Z Laurent Bercot ska-skaware@skarnet.org 2026-10-09T00:02:46Z urn:sha1:22285c3463027a3949f6a61b0ec03624c6104808 2026-10-05T18:16:38Z Laurent Bercot ska-skaware@skarnet.org 2026-10-05T18:16:38Z urn:sha1:55850e313752497880ffde33870540b0b57814c1 s6-rc-set-install is undergoing changes, it might not work properly. The rest is coming this week. 2026-10-03T02:19:00Z Laurent Bercot ska-skaware@skarnet.org 2026-10-03T02:19:00Z urn:sha1:3245c92eaa3528a4176e05ab9beaa9718afc8868 2026-10-02T02:22:28Z Laurent Bercot ska-skaware@skarnet.org 2026-10-02T02:22:28Z urn:sha1:7c93a058c8d7e21aea2aad8f3114c8422bf6faf7 In order to work across major bumps, we need to add a call to s6-rc-format-upgrade before s6-rc-update in the s6-rc-set-install sequence of commands. s6-rc-format-upgrade only works when the db is exactly the same across s6-rc versions. That means we need to have the source version of the current live set at all times, in order to compile it with the new s6-rc version before upgrading and then updating. So: 1. we take a snapshot of the source version of a set every time we commit. 2. we refuse to install if we don't have the snapshot. 3. we add s6-rc-format-upgrade to the processing chain 4. for cleanup: after installing, we delete all the snapshots of the set except the one that corresponds to the newly installed live set. This commit implements 1: taking the snapshot. It's a regular s6-rc-set-copy, using an internal name. We refactor s6-rc-set-copy and s6-rc-set-delete to have primitives we can use internally. Wait for later commits before using repo, else you'll fill your repository with snapshots that won't get cleaned up. TBD: how to store the s6-rc version in the compiled db. We probably need to add a small file in there. 2026-07-09T08:13:55Z Laurent Bercot ska-skaware@skarnet.org 2026-07-09T08:13:55Z urn:sha1:6209d961fd35c1d4e92d26c76a8ba0e98f1a6415 2026-01-24T16:17:39Z Laurent Bercot ska-skaware@skarnet.org 2026-01-24T16:17:39Z urn:sha1:7551c712d73f1d07f6dec2c9b8183a43204f4aa5