From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <zboszor@gmail.com>, <docs@lists.yoctoproject.org>
Cc: "Alexander Kanavin" <alex.kanavin@gmail.com>
Subject: Re: [docs] [PATCH 1/2] dev-manual/packages: add information about signing changes
Date: Wed, 29 Jan 2025 17:01:15 +0100 [thread overview]
Message-ID: <D7EOLBIP4NGZ.2873VJSZNHBXI@bootlin.com> (raw)
In-Reply-To: <20250129141849.838672-1-zboszor@gmail.com>
Hi Zoltán,
On Wed Jan 29, 2025 at 3:18 PM CET, Zoltan Boszormenyi via lists.yoctoproject.org wrote:
> Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
> ---
> documentation/dev-manual/packages.rst | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/documentation/dev-manual/packages.rst b/documentation/dev-manual/packages.rst
> index 4ba2dcae3..dba07a2c6 100644
> --- a/documentation/dev-manual/packages.rst
> +++ b/documentation/dev-manual/packages.rst
> @@ -819,9 +819,19 @@ to use signed package feeds (repositories) when doing a build.
> Signing RPM Packages
> --------------------
>
> -To enable signing RPM packages, you must set up the following
> -configurations in either your ``local.config`` or ``distro.config``
> -file::
> +To enable signing RPM packages, you must modify the RPM package
I would rephrase to
"""
you must modify the ``rpm`` recipe configuration to include...
"""
Because PACKAGECONFIG is a recipe-level variable, not a package-level variable.
> +configuration to include support for OpenPGP signing. That may
> +be done either in a recipe addendum called ``rpm_%.bbappend``:
This should end with :: for the code block below.
I would rather say
"""
in a ``.bbappend`` for the ``rpm`` recipe::
"""
Two reasons:
* ``.bbappend`` seems to be the most used way in the docs to denote a bbappend
* I think it's best to avoid encouraging people to use % for bbappends
> +
> + PACKAGECONFIG:append = " sequoia"
> +
> +or in either your ``local.config`` or ``distro.config`` file:
This should end with :: for the code block below.
Not your fault, but modifying local.conf is also something we try not to
encourage. And in any case, `local.config` is not a known conf file (local.conf
is).
So I would just say:
"""
...or in a :term:`Configuration File`::
"""
> +
> + PACKAGECONFIG:append:pn-rpm-native = " sequoia"
> + PACKAGECONFIG:append:pn-rpm = " sequoia"
> +
> +You must also set up the following configurations in either your
> +``local.config`` or ``distro.config`` file::
Same here as above.
>
> # Inherit sign_rpm.bbclass to enable signing functionality
> INHERIT += " sign_rpm"
Thank you,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-01-29 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 14:18 [PATCH 1/2] dev-manual/packages: add information about signing changes Zoltán Böszörményi
2025-01-29 14:18 ` [PATCH 2/2] release-notes-5.2: add information about rpm and sequoia Zoltán Böszörményi
2025-01-29 16:01 ` [docs] " Antonin Godard
2025-01-29 16:01 ` Antonin Godard [this message]
2025-01-30 9:04 ` [PATCH v2] dev-manual/packages: add information about signing changes Zoltán Böszörményi
2025-01-31 9:55 ` Antonin Godard
2025-02-12 9:09 ` Antonin Godard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D7EOLBIP4NGZ.2873VJSZNHBXI@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=zboszor@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox