From: Konrad Weihmann <kweihmann@outlook.com>
To: Scott Murray <scott.murray@konsulko.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] noexec varflag behavior vs documentation?
Date: Tue, 26 Oct 2021 19:18:18 +0200 [thread overview]
Message-ID: <AM9PR09MB4642DA41A9B3F3FCF6CB23EDA8849@AM9PR09MB4642.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <d248a56-a985-952c-363c-7a642761c2b6@spiteful.org>
On 26.10.21 17:57, Scott Murray wrote:
> As I brought up on the dev call earlier, the task noexec varflag
> documentation says:
>
> * [noexec]: When set to “1”, marks the task as being empty, with no
> execution required. You can use the [noexec] flag to set up tasks as
> dependency placeholders, or to disable tasks defined elsewhere that are
> not needed in a particular recipe.
>
> (from:
> https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html?highlight=noexec#variable-flags)
>
> However, as I discovered yesterday, the reality is that it being set to
> any value at all disables execution, which Richard mentioned on the dev
> call helps with performance. The question Richard asked me to bring here
> is whether the documentation should be updated, or if the behavior should
> be changed to match it? I do not have a strong opinion either way, but
> would like this resolved somehow to avoid others spending time scratching
> their heads like I did for a bit yesterday.
As I stumbled upon the very same, I'd love to see the docu being updated
- I mean implicitly it already does that as noexec can be only
deactivated by putting no value in it - but both cases should be
properly documented IMO
>
> Thanks,
>
> Scott
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#12833): https://lists.openembedded.org/g/bitbake-devel/message/12833
> Mute This Topic: https://lists.openembedded.org/mt/86606339/3647476
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [kweihmann@outlook.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next parent reply other threads:[~2021-10-26 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d248a56-a985-952c-363c-7a642761c2b6@spiteful.org>
2021-10-26 17:18 ` Konrad Weihmann [this message]
[not found] ` <7aabfa2b-2019-2dfb-3ae0-3ace4c4638d@spiteful.org>
[not found] ` <16B1B4E0DFE93958.19566@lists.openembedded.org>
[not found] ` <8bd2e9ff001261ae11beb8794f843965088c3162.camel@linuxfoundation.org>
2021-10-26 22:52 ` [bitbake-devel] noexec varflag behavior vs documentation? Scott Murray
2021-10-27 9:53 ` Quentin Schulz
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=AM9PR09MB4642DA41A9B3F3FCF6CB23EDA8849@AM9PR09MB4642.eurprd09.prod.outlook.com \
--to=kweihmann@outlook.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=scott.murray@konsulko.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;
as well as URLs for NNTP newsgroup(s).