s6-rc/package, branch mainThe skarnet.org service managerhttps://git.skarnet.org/cgit/s6-rc/atom/package?h=main2026-10-12T08:23:26Z Prepare for 0.8.0.0, update deps2026-10-12T08:23:26ZLaurent Bercotska-skaware@skarnet.org2026-10-12T08:23:26Zurn:sha1:1feee8fff883b4e767a79e9373a96591d46eb8a2 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.
Prepare for 0.7.1.0; add major version to every compiled db2026-10-03T02:19:00ZLaurent Bercotska-skaware@skarnet.org2026-10-03T02:19:00Zurn:sha1:3245c92eaa3528a4176e05ab9beaa9718afc8868 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.
Add -c|--clean option to s6-rc (untested)2026-07-09T08:13:55ZLaurent Bercotska-skaware@skarnet.org2026-07-09T08:13:55Zurn:sha1:6209d961fd35c1d4e92d26c76a8ba0e98f1a6415 Update deps2026-06-22T22:26:39ZLaurent Bercotska-skaware@skarnet.org2026-06-22T22:26:39Zurn:sha1:50f4e65aa2776e0916ad90130dcd28043154dfd5