From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Leon Anavi <leon.anavi@konsulko.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH] python3-setuptools-rust: Add release 0.11.6
Date: Sun, 04 Apr 2021 11:05:16 +0100 [thread overview]
Message-ID: <278df56a6cff5cd90a092c1caa416078ca5b432d.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210402114521.3888-1-leon.anavi@konsulko.com>
On Fri, 2021-04-02 at 14:45 +0300, Leon Anavi wrote:
> Add setuptools-rust release 0.11.6:
>
> - Respect CARGO_BUILD_TARGET environment variable if set.
> - Add setuptools_rust.__version__ and require setuptools >= 46.1.
>
> This recipe is required as a dependency of Python packages relying
> on Rust, for example newer versions of python3-cryptography from
> layer meta-python.
>
> Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
> ---
> .../python/python3-setuptools-rust_0.11.6.bb | 28 +++++++++++++++++++
> 1 file changed, 28 insertions(+)
> create mode 100644 meta/recipes-devtools/python/python3-setuptools-rust_0.11.6.bb
If this is targeting OE-Core (hard to tell from the subject line
including meta-oe), it has no maintainers entry. I'm also a little
surprised there is no rust dependency. Adding rust is something
we deferred to the next development cycle.
Cheers,
Richard
next prev parent reply other threads:[~2021-04-04 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 11:45 [meta-oe][PATCH] python3-setuptools-rust: Add release 0.11.6 Leon Anavi
2021-04-04 10:05 ` Richard Purdie [this message]
2021-04-05 11:44 ` [OE-core] " Leon Anavi
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=278df56a6cff5cd90a092c1caa416078ca5b432d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=leon.anavi@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.