s6-rc/src/repo/deps-lib/s6rcrepo, branch mainThe skarnet.org service managerhttps://git.skarnet.org/cgit/s6-rc/atom/src/repo/deps-lib/s6rcrepo?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.
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 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.
Rename "sub" to "prescription"2026-01-24T16:17:39ZLaurent Bercotska-skaware@skarnet.org2026-01-24T16:17:39Zurn:sha1:7551c712d73f1d07f6dec2c9b8183a43204f4aa5 Working repo fix that understands pipelines2025-12-20T23:50:19ZLaurent Bercotska-skaware@skarnet.org2025-12-20T23:50:19Zurn:sha1:b24a07fca1f2a410b3d97d1e3dc5de7720ad1d76 Next batch of fixes2025-12-09T05:46:14ZLaurent Bercotska-skaware@skarnet.org2025-12-09T05:46:14Zurn:sha1:420d8cef5cb8eed461a1b17dcd17de270571baf9 s6rc_repo_nlto0 replaced with string_index in skalibs2025-11-10T05:22:36ZLaurent Bercotska-skaware@skarnet.org2025-11-10T05:22:36Zurn:sha1:9c04967220922921b83827665e0ae141a43d237c Separate libs6rcrepo2025-10-22T22:05:56ZLaurent Bercotska-skaware@skarnet.org2025-10-22T22:05:56Zurn:sha1:e0bcc0ef3466b7b5fc776d2e78d7e7ec027810c0