diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2026-10-02 02:22:28 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2026-10-02 02:22:28 +0000 |
| commit | 7c93a058c8d7e21aea2aad8f3114c8422bf6faf7 (patch) | |
| tree | ae569edcc313796b679ec8374e50668c973ffd5f /doc/index.html | |
| parent | 3a151bcd1835e1f7871a93c5b0d90f856562a98a (diff) | |
| download | s6-rc-7c93a058c8d7e21aea2aad8f3114c8422bf6faf7.tar.gz | |
First part of the format-upgrade support in repo
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.
Diffstat (limited to 'doc/index.html')
0 files changed, 0 insertions, 0 deletions
