From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
<docs@lists.yoctoproject.org>
Cc: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH] ref-manual: faq: add q&a on class appends
Date: Thu, 24 Oct 2024 11:29:22 +0200 [thread overview]
Message-ID: <D53XIFGXLTYO.1UJ2C08736DBF@bootlin.com> (raw)
In-Reply-To: <368af907-7c85-4e27-812b-f608f1d2b8dd@cherry.de>
Hi Quentin,
On Thu Oct 24, 2024 at 11:27 AM CEST, Quentin Schulz wrote:
> Hi Antonin,
>
> On 10/24/24 11:14 AM, Antonin Godard via lists.yoctoproject.org wrote:
>> Add the suggestion by Richard to the FAQ, with some minor rewordings and
>> additional punctuations.
>>
>> Suggested-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>> documentation/ref-manual/faq.rst | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst
>> index bab284bbfdefae02c284204d3c94891a8238239a..3dcb1f862e24716be703f9fd3e811d2fb9ed34a0 100644
>> --- a/documentation/ref-manual/faq.rst
>> +++ b/documentation/ref-manual/faq.rst
>> @@ -259,6 +259,25 @@ Within the :term:`Build Directory`, is the ``tmp`` directory. To remove all the
>> build output yet preserve any source code or downloaded files from
>> previous builds, simply remove the ``tmp`` directory.
>>
>> +Why isn't there a way to append bbclass files like bbappend for recipes?
>> +------------------------------------------------------------------------
>> +
>> +The Yocto Project has consciously chosen not to implement such functionality.
>> +Class code is designed to be shared and reused, and expose some level of
>
> s/expose/exposes/
>
> except if we meant "class code is designed to expose" rather than "class
> code exposes"
Agreed it should probably by exposes here.
>> +configuration to its users. We want to encourage people to share these changes
>> +so we can build the best classes.
>> +
>> +If the ``append`` functionality was available for classes, our evidence and
>> +experience suggests that people would create their custom changes in their
>
> s/suggests/suggest/ (evidence+experience)
Good catch. :)
> Otherwise looks good to me :)
>
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
>
> Cheers,
> Quentin
Thank you!
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-10-24 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 9:14 [PATCH] ref-manual: faq: add q&a on class appends Antonin Godard
2024-10-24 9:27 ` [docs] " Quentin Schulz
2024-10-24 9:29 ` Antonin Godard [this message]
2024-10-24 10:31 ` Richard Purdie
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=D53XIFGXLTYO.1UJ2C08736DBF@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=richard.purdie@linuxfoundation.org \
--cc=thomas.petazzoni@bootlin.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