5a79ca9035
Came out of discussion in https://github.com/coreos/rpm-ostree/pull/2581 around some racy code for checking for the live commit object. The reliability of apply-live depends on the underlying commits not being garbage collected. Our diff logic is in terms of ostree commits, not the physical filesystem (this allows us to make various optimizations too). Ultimately I think we should drive some of the live-apply logic into libostree itself; we can more easily have an atomic state file instead of the two split refs. (Or perhaps what we should add to ostree is like a refs.d model where a single atomic file can refer to multiple commits) For now though let's rework the code here to write refs. We retain the file in `/run` as just a "stamp file" that signals that a deployment has had `apply-live` run. |
||
|---|---|---|
| .. | ||
| destructive | ||
| nondestructive | ||
| Makefile | ||