diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-03-08 10:10:12 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2022-03-29 16:17:56 +0200 |
| commit | 3a84a3c9dfde5182398a6d0863a2b2fe90a936b1 (patch) | |
| tree | 5adbe2ae09f288bb978473eb0c41e1f1635473e9 /man/os-release.xml | |
| parent | 25407ad2a785d10b1aadff0c99829ea0cf51082b (diff) | |
| download | systemd-3a84a3c9dfde5182398a6d0863a2b2fe90a936b1.tar.gz | |
man/os-release: add a note about repeating entries
We didn't actually say that keys should not be repeated. At least the
examples in docs (both python and shell) would do that, and any simple
parser that builds a dictionary would most likely behave the same way.
But let's document this expectation, but also say how to deal with malformed
files.
Diffstat (limited to 'man/os-release.xml')
| -rw-r--r-- | man/os-release.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/man/os-release.xml b/man/os-release.xml index 4acd1a9a57..7e3e9a73a8 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -75,6 +75,10 @@ from earliest boot on, and hence must be located on the root file system.</para> + <para><filename>os-release</filename> must not contain repeating keys. Nevertheless, readers should pick + the entries later in the file in case of repeats, similarly to how a shell sourcing the file would. A + reader may warn about repeating entries.</para> + <para>For a longer rationale for <filename>os-release</filename> please refer to the <ulink url="http://0pointer.de/blog/projects/os-release">Announcement of <filename>/etc/os-release</filename></ulink>.</para> |