From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Mützel" <andreas.muetzel@emlix.com>,
poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH] python3-bcrypt: allow building native package
Date: Tue, 27 Feb 2024 11:32:45 +0000 [thread overview]
Message-ID: <deaee499fe278f479d0e1583426e4b2f62389d32.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240227101522.3155724-1-andreas.muetzel@emlix.com>
On Tue, 2024-02-27 at 11:15 +0100, Andreas Mützel wrote:
> The native and nativesdk variants of this package build fine, but the
> corresponding BBCLASSEXTENDS was missing. Add it.
>
> Signed-off-by: Andreas Mützel <andreas.muetzel@emlix.com>
> ---
> meta/recipes-devtools/python/python3-bcrypt_4.1.2.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-devtools/python/python3-bcrypt_4.1.2.bb
> b/meta/recipes-devtools/python/python3-bcrypt_4.1.2.bb
> index 8328594bad..72216c39c2 100644
> --- a/meta/recipes-devtools/python/python3-bcrypt_4.1.2.bb
> +++ b/meta/recipes-devtools/python/python3-bcrypt_4.1.2.bb
> @@ -34,3 +34,5 @@ RDEPENDS:${PN}:class-target += "\
> python3-shell \
> python3-six \
> "
> +
> +BBCLASSEXTEND = "native nativesdk"
As well as sending to the correct list, could you add a bit more
justification/information about what needs this?
Adding these variants isn't "free" as it has parsing and maintenance
overhead so we try not to add this unless we need to.
Cheers,
Richard
prev parent reply other threads:[~2024-02-27 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 10:15 [PATCH] python3-bcrypt: allow building native package Andreas Mützel
2024-02-27 11:27 ` [poky] " Ross Burton
2024-02-27 11:32 ` Richard Purdie [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=deaee499fe278f479d0e1583426e4b2f62389d32.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andreas.muetzel@emlix.com \
--cc=poky@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).