From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v12.1 1/5] rpm-sequoia-crypto-policy: New recipe
Date: Sat, 22 Feb 2025 08:56:40 +0100 [thread overview]
Message-ID: <bc48230a-d3b5-4df5-b282-e3a883f361e4@gmail.com> (raw)
In-Reply-To: <CA355874-B96E-49C4-A338-06225BDAA8ED@arm.com>
2025. 02. 20. 15:43 keltezéssel, Ross Burton írta:
> On 13 Feb 2025, at 15:21, Zoltan Boszormenyi via lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org> wrote:
>> +DEPENDS = "coreutils-native openssl-native make-native"
>> +
>> +inherit allarch python3native
> These dependencies seem unexpected, and if they’re needed then they should be explained.
>
> We assume make on the host, so why do you need make-native? If there’s a good reason, please comment why.
>
> Ditto for coreutils-native: presumably there’s a tool that isn’t in HOSTTOOLS? What tool?
>
> Typically there’s no need to inherit python3native unless you’re also depending on python3-something-native modules, as by definition there’s a capable python interpreter as it’s running bitbake.
Thanks, I will send a followup patch after testing the dependency changes.
>
> Thanks,
> Ross
next prev parent reply other threads:[~2025-02-22 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 4:35 [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe Zoltán Böszörményi
2025-02-12 4:35 ` [OE-core][PATCH v12 2/5] rpm-sequoia: New recipe for version 1.7.0 Zoltán Böszörményi
2025-02-12 4:35 ` [OE-core][PATCH v12 3/5] rpm: Set SEQUOIA_CRYPTO_POLICY in wrapped tools Zoltán Böszörményi
2025-02-12 4:35 ` [OE-core][PATCH v12 4/5] dnf: " Zoltán Böszörményi
2025-02-12 4:35 ` [OE-core][PATCH v12 5/5] oeqa/selftest/cases/signing.py: Re-enable self-test Zoltán Böszörményi
2025-02-13 13:36 ` [OE-core][PATCH v12 1/5] rpm-sequoia-crypto-policy: New recipe Mathieu Dubois-Briand
2025-02-13 14:20 ` Böszörményi Zoltán
2025-02-13 14:32 ` Richard Purdie
2025-02-13 14:40 ` Böszörményi Zoltán
[not found] ` <1823CA649EDDAA06.9844@lists.openembedded.org>
2025-02-13 14:43 ` Böszörményi Zoltán
2025-02-13 15:06 ` Richard Purdie
2025-02-13 15:14 ` Böszörményi Zoltán
2025-02-13 15:16 ` Alexander Kanavin
2025-02-13 15:27 ` Böszörményi Zoltán
2025-02-13 15:17 ` Richard Purdie
[not found] ` <1823CBAB98621FC2.9844@lists.openembedded.org>
2025-02-13 15:09 ` Böszörményi Zoltán
2025-02-13 15:21 ` [OE-core][PATCH v12.1 " Zoltán Böszörményi
2025-02-20 14:43 ` Ross Burton
2025-02-22 7:56 ` Böszörményi Zoltán [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 15:23 Zoltán Böszörményi
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=bc48230a-d3b5-4df5-b282-e3a883f361e4@gmail.com \
--to=zboszor@gmail.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
/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