1
0
mirror of https://github.com/systemd/systemd.git synced 2025-02-07 05:57:46 +03:00

man: update package metadata link and details

The variable names are actually "name" and "version". Not sure why the
man page had something different.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2024-12-19 15:32:55 +01:00
parent bafe34ddbe
commit 06a73d1fb6
2 changed files with 11 additions and 8 deletions

View File

@ -862,8 +862,9 @@ alias.service:7: Unknown key name 'MysteryKey' in section 'Service', ignoring.
<para>This command will load the specified files, and if they are ELF objects (executables,
libraries, core files, etc.) it will parse the embedded packaging metadata, if any, and print
it in a table or json format. See the <ulink url="https://systemd.io/COREDUMP_PACKAGE_METADATA/">
Packaging Metadata</ulink> documentation for more information.</para>
it in a table or json format. See the
<ulink url="https://systemd.io/PACKAGE_METADATA_FOR_EXECUTABLE_FILES/">
Package Metadata for Executable Files</ulink> document for more information.</para>
<example>
<title>Print information about a core file as JSON</title>

View File

@ -412,12 +412,14 @@ flags: ...
<term><varname>COREDUMP_PACKAGE_VERSION=</varname></term>
<term><varname>COREDUMP_PACKAGE_JSON=</varname></term>
<listitem><para>If the executable contained .package metadata ELF notes, they will be
parsed and attached. The <varname>package</varname> and <varname>packageVersion</varname>
of the 'main' ELF module (ie: the executable) will be appended individually. The
JSON-formatted content of all modules will be appended as a single JSON object, each with
the module name as the key. For more information about this metadata format and content, see
<ulink url="https://systemd.io/COREDUMP_PACKAGE_METADATA/">the coredump metadata spec</ulink>.</para>
<listitem><para>If the executable contained .package metadata ELF notes, they will be parsed and
attached. The <varname>package</varname> and <varname>version</varname> of the 'main' ELF module
(i.e., the executable) will be appended individually. The JSON-formatted content of all modules will
be appended as a single JSON object, each with the module name as the key. For more information about
this metadata format and content, see the
<ulink url="https://systemd.io/PACKAGE_METADATA_FOR_EXECUTABLE_FILES/">Package Metadata for Executable Files</ulink>
document.
</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>