From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: quentin.schulz@theobroma-systems.com,
Mikko Rapeli <mikko.rapeli@linaro.org>,
openembedded-core@lists.openembedded.org,
docs@lists.yoctoproject.org
Subject: Re: [OE-core] [docs] [PATCH 1/7] common-tasks.rst: remove SRC_URI:append from examples
Date: Mon, 19 Sep 2022 21:35:50 +0100 [thread overview]
Message-ID: <1a076f35-655f-bf9a-cb11-8489958ea829@bootlin.com> (raw)
In-Reply-To: <f0c891d5-ccdd-41fb-97b9-ce987818e18f@theobroma-systems.com>
Mikko, thanks for the patch series.
Quentin, thanks for the review.
Indeed, I think that the description of the commit should be improved
too. See below.
On 9/19/22 16:04, Quentin Schulz via lists.openembedded.org wrote:
> Hi Mikko,
>
> On 9/12/22 09:32, Mikko Rapeli wrote:
>> Using SRC_URI:append without recipe, machine or architecture
>> specific limitations makes the :append'ed text unremovable
>> and thus users and custom layers can not change the variable
>> anymore. This makes it hard to e.g. override SRC_URI completely
>> in a bbappend to update the full recipe to a newer version.
>> Thus common, reusable layers which users are meant to re-use and
>> customize should not use SRC_URI:append but SRC_URI += instead.
What the following text instead?
Using SRC_URI:append without recipe, machine or architecture specific
limitations makes the :append'ed text more difficult to override than if
the "+=" operator was used. This makes it hard for example to override
SRC_URI completely in a bbappend to update the full recipe to a newer
version. Thus common, reusable layers which users are meant to re-use
and customize should not use SRC_URI:append but SRC_URI += instead.
>>
>> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
>> ---
>> documentation/dev-manual/common-tasks.rst | 9 +++++----
>> 1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/documentation/dev-manual/common-tasks.rst
>> b/documentation/dev-manual/common-tasks.rst
>> index b08a55331d..3112f9b893 100644
>> --- a/documentation/dev-manual/common-tasks.rst
>> +++ b/documentation/dev-manual/common-tasks.rst
>> @@ -2577,7 +2577,7 @@ chapter of the BitBake User Manual.
>> S = "${WORKDIR}/postfix-${PV}"
>> CFLAGS += "-DNO_ASM"
>> - SRC_URI:append = " file://fixup.patch"
>> + CFLAGS:append = " --enable-important-feature"
Didn't you mean
+ SRC_URI += "file://fixup.patch"
instead here?
>> - *Functions:* Functions provide a series of actions to be
>> performed.
>> You usually use functions to override the default implementation
>> of a
>> @@ -2708,19 +2708,20 @@ in the BitBake User Manual.
>> to existing variables. This operator does not add any additional
>> space. Also, the operator is applied after all the ``+=``, and
>> ``=+``
>> operators have been applied and after all ``=`` assignments have
>> - occurred.
>> + occurred. This means that if ``:append`` is used, that text can
>> not be
>> + removed.
>
> Pedantic: it can, with :remove. One should try really hard to not use
> it though.
What about...
"This means that if ``:append`` is used in a recipe, it cannot only be
overridden by another layer using the special ``:remove`` operator,
which in turn will prevent further layers from adding it back."
I'm not very happy with this wording, because ":remove" hasn't been
introduced at this stage in this section. Maybe we should add a link
to https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#conditional-syntax-overrides
Any thoughts?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-09-19 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 7:32 [PATCH 1/7] common-tasks.rst: remove SRC_URI:append from examples Mikko Rapeli
2022-09-12 7:32 ` [PATCH 2/7] kernel-dev/common.rst: " Mikko Rapeli
2022-09-12 7:32 ` [PATCH 3/7] u-boot: switch from append to += in SRC_URI Mikko Rapeli
2022-09-12 7:32 ` [PATCH 4/7] glibc-tests: use += instead of :append Mikko Rapeli
2022-09-12 7:32 ` [PATCH 5/7] go-native: switch from SRC_URI:append to SRC_URI += Mikko Rapeli
2022-09-12 7:32 ` [PATCH 6/7] python3-rfc3986-validator: " Mikko Rapeli
2022-09-12 7:32 ` [PATCH 7/7] linux-libc-headers: " Mikko Rapeli
2022-09-19 15:04 ` [docs] [PATCH 1/7] common-tasks.rst: remove SRC_URI:append from examples Quentin Schulz
2022-09-19 20:35 ` Michael Opdenacker [this message]
2022-09-20 7:34 ` [OE-core] " Mikko Rapeli
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=1a076f35-655f-bf9a-cb11-8489958ea829@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@theobroma-systems.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