From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Simone Weiß" <simone.p.weiss@posteo.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] bitbake-layers: add/remove option to not use tinfoil
Date: Tue, 26 Mar 2024 11:48:47 +0000 [thread overview]
Message-ID: <c361e70b826c31cfa03b057557ab1f5421ca673d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240325202757.7711-1-simone.p.weiss@posteo.com>
On Mon, 2024-03-25 at 20:27 +0000, Simone Weiß wrote:
> From: Simone Weiß <simone.p.weiss@posteo.com>
>
> Fixes [YOCTO #15417]
>
> When a layer adds a new dependency after it was added to a conf, it
> can not be
> removed w/o this dependency in the setup. Even the dependent layer
> can not be
> added, as the tinfoil setup will fail.
> Add an option to not perform the tinfoil at all, the use will be at
> own risk,
> i.e. the added layers might not parse properly afterwards.
>
> Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com>
> ---
> bin/bitbake-layers | 16 +++++++++++-----
> lib/bblayers/action.py | 6 ++++--
> 2 files changed, 15 insertions(+), 7 deletions(-)
Rather than calling this "notinfoil", which won't mean much to users,
we should probably call it something which means "skip parsing tests"
or similar. That way people would understand what it does.
Cheers,
Richard
next prev parent reply other threads:[~2024-03-26 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 20:27 [PATCH] bitbake-layers: add/remove option to not use tinfoil simone.p.weiss
2024-03-26 11:48 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-30 16:46 simone.p.weiss
2024-04-02 13:29 ` [bitbake-devel] " Richard Purdie
2024-04-02 20:51 ` Simone Weiß
2024-04-10 20:13 ` Simone Weiß
2024-04-11 16:11 ` 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=c361e70b826c31cfa03b057557ab1f5421ca673d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=simone.p.weiss@posteo.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 read-only IMAP folder(s) and NNTP newsgroup(s).