From: Nils K <24257556+septatrix@users.noreply.github.com>
Date: Thu, 10 Oct 2024 14:06:48 +0000 (+0200)
Subject: Clarify explanation of `Verity=` option
X-Git-Tag: v25~222
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=90874571f6874f00ca76104f46a6c97e5a65bd2e;p=thirdparty%2Fmkosi.git

Clarify explanation of `Verity=` option

This clarifies that the "auto" value for the verity option
only really makes sense for extension images.
---

diff --git a/mkosi/resources/man/mkosi.1.md b/mkosi/resources/man/mkosi.1.md
index 52c617962..41c2ac5a3 100644
--- a/mkosi/resources/man/mkosi.1.md
+++ b/mkosi/resources/man/mkosi.1.md
@@ -1136,9 +1136,9 @@ boolean argument: either `1`, `yes`, or `true` to enable, or `0`, `no`,
     certificate must be present and the build will fail if we don't
     detect any verity partitions in the disk image produced by
     systemd-repart. If disabled, verity partitions will be excluded from
-    disk images produced by systemd-repart even if the partition
-    definitions contain verity partitions. If set to `auto`, the verity
-    key and certificate will be passed to systemd-repart if available,
+    the extension images produced by systemd-repart. If set to `auto` and
+    a verity key and certificate are present, mkosi will pass them to systemd-repart
+    and expects the generated disk image to contain verity partitions,
     but the build won't fail if no verity partitions are found in the
     disk image produced by systemd-repart.