s6-rc/src/repo, branch mainThe skarnet.org service managerhttps://git.skarnet.org/cgit/s6-rc/atom/src/repo?h=main2026-10-15T08:19:48Z More work on format-upgrade inclusion: real meta-information storage2026-10-15T08:19:48ZLaurent Bercotska-skaware@skarnet.org2026-10-15T08:19:48Zurn:sha1:db3fb428599c9c8fe105dcf4ba8d1c914c54cc26
If a db format upgrade is necessary, we need to compile the snapshot
with the new s6-rc-compile. There's data we need to pass to it that
isn't stored (options passed when committing the original set), so
we store it in the db itself (patching s6-rc-compile). We modify
the s6-rc-compile wrappers to pass all this metadata.
Next, we will compile the snapshot.
Second part of the format-upgrade support: ensure snapshots are there2026-10-15T05:17:26ZLaurent Bercotska-skaware@skarnet.org2026-10-15T05:17:26Zurn:sha1:91a0655557e707977f583b2142bda898ee599fd8
We don't want to install compiled dbs without having a snapshot of
their source set, so whenever we test that the compiled db is up to
date, we also test that a snapshot is present. This is important
because we will auto-cleanup unused snapshots after installation.
But this day is not today, so screw it. We gotta keep em separated2026-10-09T00:59:02ZLaurent Bercotska-skaware@skarnet.org2026-10-09T00:59:02Zurn:sha1:c71344185cc93d9322513a1d9506cb14b1c308a2 Someday I'll figure out dynamic libraries dependencies with rpath2026-10-09T00:40:33ZLaurent Bercotska-skaware@skarnet.org2026-10-09T00:40:33Zurn:sha1:a6883e06261447cec639c6d260270ec0664c2153 Maybe maybe maybe2026-10-09T00:30:42ZLaurent Bercotska-skaware@skarnet.org2026-10-09T00:30:42Zurn:sha1:99ff79f0db04a70e46ac0f2717979ab25de75a78 Fix build, maybe?2026-10-09T00:02:46ZLaurent Bercotska-skaware@skarnet.org2026-10-09T00:02:46Zurn:sha1:22285c3463027a3949f6a61b0ec03624c6104808 Propagate -L catchall changes to s6-rc-set-commit2026-10-05T18:16:38ZLaurent Bercotska-skaware@skarnet.org2026-10-05T18:16:38Zurn:sha1:55850e313752497880ffde33870540b0b57814c1
s6-rc-set-install is undergoing changes, it might not work
properly. The rest is coming this week.
First part of the format-upgrade support in repo2026-10-02T02:22:28ZLaurent Bercotska-skaware@skarnet.org2026-10-02T02:22:28Zurn: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.
s6-rc-set-change: move if-dependencies tristate to two bools2026-06-15T20:23:02ZLaurent Bercotska-skaware@skarnet.org2026-06-15T20:23:02Zurn:sha1:968a4dfecc4340dcfedf9d231e7465710219f762 Cleanup on s6-rc-repo-init sync error2026-05-12T17:49:59ZLaurent Bercotska-skaware@skarnet.org2026-05-12T17:49:59Zurn:sha1:aaeca3823cf4ef4e2f6e68bfb2af0c5b52b1721c