diff options
| author | Colin Walters <walters@verbum.org> | 2021-03-11 01:36:13 +0000 |
|---|---|---|
| committer | Colin Walters <walters@verbum.org> | 2021-03-12 19:01:42 +0000 |
| commit | 857587615dc36d2d99e1a9bd36486f4267298971 (patch) | |
| tree | daa91a2fa072e7a184f8ddf73d0ed86a30db44d0 /man | |
| parent | 31e19935b509d65c835639b9eaf4ac553aa61655 (diff) | |
| download | ostree-857587615dc36d2d99e1a9bd36486f4267298971.tar.gz | |
Add an API+CLI to inject metadata for bootable OSTree commits
I was doing some rpm-ostree work and I wanted to compare two
OSTree commits to see if the kernel has changed. I think
this should be a lot more natural.
Add `ostree commit --bootable` which calls into a new generic
library API `ostree_commit_metadata_for_bootable()` that
discovers the kernel version and injects it as an `ostree.linux`
metadata key. And for extra clarity, add an `ostree.bootable`
key.
It's interesting because the "core" OSTree layer is all about
generic files, but this is adding special APIs around bootable
OSTree commits (as opposed to e.g. flatpak as well as
things like rpm-ostree's pkgcache refs).
Eventually, I'd like to ensure everyone is using this and
hard require this metadata key for the `ostree admin deploy`
flow - mainly to prevent accidents.
Diffstat (limited to 'man')
| -rw-r--r-- | man/ostree-commit.xml | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/man/ostree-commit.xml b/man/ostree-commit.xml index ab5d3415..81af7bf2 100644 --- a/man/ostree-commit.xml +++ b/man/ostree-commit.xml @@ -187,6 +187,13 @@ Boston, MA 02111-1307, USA. </varlistentry> <varlistentry> + <term><option>--bootable</option></term> + <listitem><para> + Inject standard metadata for a bootable Linux filesystem tree. + </para></listitem> + </varlistentry> + + <varlistentry> <term><option>--link-checkout-speedup</option></term> <listitem><para> |