From: "Joshua Watt" <JPEWhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: jdmason@kudzu.us, denis@denix.org, Joshua Watt <JPEWhacker@gmail.com>
Subject: [OE-core][PATCH 0/4] Import recipes from meta-python
Date: Thu, 14 May 2020 16:04:54 -0500 [thread overview]
Message-ID: <20200514210458.33543-1-JPEWhacker@gmail.com> (raw)
Imports and upgrades pycryptodome, pycryptodomex, and pyelftools from
meta-python. These recipes are commonly used by other layers (e.g.
meta-arm) so putting them in oe-core reduces layer dependencies.
Joshua Watt (4):
pycryptodome: Import from meta-python
pyelftools: Import from meta-python
python3-pycryptodome(x): Upgrade 3.9.4 -> 3.9.7
python3-pyelftools: Upgrade 0.25 -> 0.26
meta/conf/distro/include/maintainers.inc | 5 +++-
.../python/python-pycryptodome.inc | 26 +++++++++++++++++++
.../python/python3-pycryptodome_3.9.7.bb | 5 ++++
.../python/python3-pycryptodomex_3.9.7.bb | 9 +++++++
.../python/python3-pyelftools_0.26.bb | 14 ++++++++++
5 files changed, 58 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-devtools/python/python-pycryptodome.inc
create mode 100644 meta/recipes-devtools/python/python3-pycryptodome_3.9.7.bb
create mode 100644 meta/recipes-devtools/python/python3-pycryptodomex_3.9.7.bb
create mode 100644 meta/recipes-devtools/python/python3-pyelftools_0.26.bb
--
2.17.1
next reply other threads:[~2020-05-14 21:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 21:04 Joshua Watt [this message]
2020-05-14 21:04 ` [OE-core][PATCH 1/4] pycryptodome: Import from meta-python Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 2/4] pyelftools: " Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 3/4] python3-pycryptodome(x): Upgrade 3.9.4 -> 3.9.7 Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 4/4] python3-pyelftools: Upgrade 0.25 -> 0.26 Joshua Watt
2020-05-15 18:53 ` [OE-core][PATCH 0/4] Import recipes from meta-python Denys Dmytriyenko
2020-05-15 19:05 ` Richard Purdie
2020-05-15 19:12 ` Joshua Watt
2020-05-15 19:26 ` Denys Dmytriyenko
2020-05-15 19:56 ` Andrey Zhizhikin
2020-05-15 19:32 ` Khem Raj
2020-05-17 1:05 ` Alejandro Hernandez
2020-05-16 1:21 ` Steve Sakoman
2020-05-16 17:47 ` Adrian Bunk
2020-05-16 19:54 ` Peter Kjellerstedt
2020-05-16 20:09 ` Adrian Bunk
2020-05-16 20:24 ` Andrey Zhizhikin
2020-05-16 23:15 ` Andre McCurdy
2020-05-17 13:22 ` Adrian Bunk
2020-05-17 13:56 ` Martin Jansa
2020-05-17 15:45 ` Adrian Bunk
2020-05-17 16:00 ` Martin Jansa
2020-05-17 16:14 ` Adrian Bunk
2020-05-17 23:47 ` Khem Raj
2020-05-19 18:20 ` Steve Sakoman
2020-05-19 18:24 ` Martin Jansa
2020-05-19 19:57 ` Andre McCurdy
2020-05-21 9:11 ` Martin Jansa
2020-05-17 23:45 ` Khem Raj
2020-05-17 23:41 ` Khem Raj
2020-05-18 6:41 ` Alejandro Hernandez
2020-05-17 23:38 ` Khem Raj
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=20200514210458.33543-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--cc=denis@denix.org \
--cc=jdmason@kudzu.us \
--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