From: Quentin Schulz <quentin.schulz@cherry.de>
To: rpjday@crashcourse.ca,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] any value in clarifying PROVIDES "=" versus "+="?
Date: Wed, 22 Apr 2026 18:11:33 +0200 [thread overview]
Message-ID: <7ce54901-e56b-4664-8c14-28dcc79a71d2@cherry.de> (raw)
In-Reply-To: <010efd6d-de6d-28b1-b195-e28c3d3a25a7@crashcourse.ca>
Hi Robert,
On 3/12/26 2:29 PM, Robert P. J. Day via lists.yoctoproject.org wrote:
>
> i remember some time ago there was a short discussion about:
>
> https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-execution.html#providers
>
> where that section *appears* to suggest that one should use "+=" when
> extending a recipe's PROVIDES which, as we all know, is technically
> not true since "=" is sufficient, *but* IIRC, richard purdie weighed
> in and suggested that, sure, one needs only "=" *but* "+=" is more
> visually intuitive, so should that section be reworded in any way, or
> left as is? (i think it needs some rewording since that explanation
> will not match what people perusing the code will find, and they will
> get confused.)
>
Maybe a note if you want to highlight that PROVIDES = "fullkeyboard"
will do the same thing but we recommend people using += to hint that an
implicit value is also available.
Patches welcome as usual. Sometimes sending a patch takes less time than
asking whether it's welcome, wait for someone to answer and then send
it. Also, patches have a much higher chance of being looked at compared
to non-patch mails like this one.
Cheers,
Quentin
prev parent reply other threads:[~2026-04-22 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 13:29 any value in clarifying PROVIDES "=" versus "+="? Robert P. J. Day
2026-04-22 16:11 ` Quentin Schulz [this message]
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=7ce54901-e56b-4664-8c14-28dcc79a71d2@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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