From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <bhstalel@gmail.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs][PATCH 1/2] ref-manual/classes.rst: add details about actions done by base.bbclass
Date: Mon, 22 Sep 2025 16:32:09 +0200 [thread overview]
Message-ID: <DCZEHNS2J0WG.2PV5B9HWKUBSV@bootlin.com> (raw)
In-Reply-To: <20250921164306.53501-2-bhstalel@gmail.com>
On Sun Sep 21, 2025 at 6:43 PM CEST, BELHADJ SALEM Talel via lists.yoctoproject.org wrote:
> Signed-off-by: Talel BELHAJ SALEM <bhstalel@gmail.com>
> ---
> documentation/ref-manual/classes.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> index 662121ed9..791c6b2ef 100644
> --- a/documentation/ref-manual/classes.rst
> +++ b/documentation/ref-manual/classes.rst
> @@ -183,6 +183,14 @@ The class also contains some commonly used functions such as
> :term:`EXTRA_OEMAKE` variable as well as the
> arguments passed directly to ``oe_runmake``.
>
> +The following actions, among others, are handled by this class:
I would perhaps phrase this differently, how about:
"""
For example, the following items are handled by this class:
"""
So intent is more about giving some examples about what the class is doing.
> +
> +- Define default dependencies and add them to :term:`DEPENDS` if :term:`INHIBIT_DEFAULT_DEPS`
> + is not defined
What dependencies? I'm afraid adding this sentence may add confusion instead of
adding precision.
> +- Handle :term:`PACKAGECONFIG` variable
This is vague too. I would extend this sentence to briefly give some context.
> +- Handle the provided license via :term:`LICENSE` and :term:`LIC_FILES_CHKSUM` variables
s/license/license(s)
This is again a bit vague, I'm not sure what's the added value. How about:
"""
Handle the provided license(s) specified in the :term:`LICENSE` variable, and
verify its checksum specified in the :term:`LIC_FILES_CHKSUM` variable.
"""
> +- Prepare the native recipe that correspond to the scheme set in :term:`SRC_URI`
This is too vague, I'm not sure what you wanted to convey here.
> +
> .. _ref-classes-bash-completion:
>
> ``bash-completion``
I would finish by saying:
"""
See the source code of the :ref:`ref-classes-base` class to get a complete
overview of what the class handles.
"""
So that way we insist on the fact that we were just giving examples.
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-09-22 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 16:43 [docs][PATCH 0/2] Add more details about the behaviour of the base class Talel BELHAJ SALEM
2025-09-21 16:43 ` [docs][PATCH 1/2] ref-manual/classes.rst: add details about actions done by base.bbclass Talel BELHAJ SALEM
2025-09-22 14:32 ` Antonin Godard [this message]
2025-09-22 18:05 ` Talel BELHADJ SALEM
[not found] ` <1867ACF8FB1FE7F2.23261@lists.yoctoproject.org>
2025-09-22 18:12 ` Talel BELHADJ SALEM
2025-09-23 16:15 ` Antonin Godard
2025-09-25 14:55 ` Talel BELHADJ SALEM
2025-09-25 15:11 ` Antonin Godard
2025-09-21 16:43 ` [docs][PATCH 2/2] ref-manual/classes.rst: add diagram for classes used " Talel BELHAJ SALEM
2025-09-25 14:29 ` Antonin Godard
2025-09-25 18:00 ` Gyorgy Sarvari
2025-09-30 11:18 ` Talel BELHADJ SALEM
2025-10-02 8:06 ` 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=DCZEHNS2J0WG.2PV5B9HWKUBSV@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bhstalel@gmail.com \
--cc=docs@lists.yoctoproject.org \
/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