From: "akuster" <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-python][PATCH 3/5] python3-rsa: add new package
Date: Fri, 10 Jul 2020 20:19:30 -0700 [thread overview]
Message-ID: <20200711031932.5883-3-akuster808@gmail.com> (raw)
In-Reply-To: <20200711031932.5883-1-akuster808@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
.../python/python3-rsa_3.4.2.bb | 44 +++++++++++++++++++
1 file changed, 44 insertions(+)
create mode 100644 meta-python/recipes-devtools/python/python3-rsa_3.4.2.bb
diff --git a/meta-python/recipes-devtools/python/python3-rsa_3.4.2.bb b/meta-python/recipes-devtools/python/python3-rsa_3.4.2.bb
new file mode 100644
index 0000000000..759214fa38
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python3-rsa_3.4.2.bb
@@ -0,0 +1,44 @@
+SUMMARY = "Pure-Python RSA implementation"
+SECTION = "devel/python"
+AUTHOR = "Sybren A. Stuvel"
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c403f6882d4f97a9cd927df987d55634"
+
+SRC_URI[sha256sum] = "25df4e10c263fb88b5ace923dd84bf9aa7f5019687b5e55382ffcdb8bede9db5"
+
+inherit pypi setuptools3 update-alternatives
+
+ALTERNATIVE_${PN} = "\
+ pyrsa-decrypt \
+ pyrsa-decrypt-bigfile \
+ pyrsa-encrypt \
+ pyrsa-encrypt-bigfile \
+ pyrsa-keygen \
+ pyrsa-priv2pub \
+ pyrsa-sign \
+ pyrsa-verify \
+"
+
+ALTERNATIVE_LINK_NAME[pyrsa-decrypt] = "${bindir}/pyrsa-decrypt"
+ALTERNATIVE_LINK_NAME[pyrsa-decrypt-bigfile] = "${bindir}/pyrsa-decrypt-bigfile"
+ALTERNATIVE_LINK_NAME[pyrsa-encrypt] = "${bindir}/pyrsa-encrypt"
+ALTERNATIVE_LINK_NAME[pyrsa-encrypt-bigfile] = "${bindir}/pyrsa-encrypt-bigfile"
+ALTERNATIVE_LINK_NAME[pyrsa-keygen] = "${bindir}/pyrsa-keygen"
+ALTERNATIVE_LINK_NAME[pyrsa-priv2pub] = "${bindir}/pyrsa-priv2pub"
+ALTERNATIVE_LINK_NAME[pyrsa-sign] = "${bindir}/pyrsa-sign"
+ALTERNATIVE_LINK_NAME[pyrsa-verify] = "${bindir}/pyrsa-verify"
+ALTERNATIVE_PRIORITY = "30"
+
+
+RDEPENDS_${PN} += "\
+ ${PYTHON_PN}-compression \
+ ${PYTHON_PN}-crypt \
+ ${PYTHON_PN}-doctest \
+ ${PYTHON_PN}-logging \
+ ${PYTHON_PN}-math \
+ ${PYTHON_PN}-multiprocessing \
+ ${PYTHON_PN}-netclient \
+ ${PYTHON_PN}-pickle \
+"
+
+RDEPENDS_${PN} += "${PYTHON_PN}-pyasn1"
--
2.17.1
next prev parent reply other threads:[~2020-07-11 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 3:19 [meta-python][PATCH 1/5] python3-gmpy2: add new package akuster
2020-07-11 3:19 ` [meta-python][PATCH 2/5] python3-ecdsa: add package akuster
2020-07-15 23:52 ` [oe] " Trevor Gamblin
2020-07-11 3:19 ` akuster [this message]
2020-07-15 23:52 ` [oe] [meta-python][PATCH 3/5] python3-rsa: add new package Trevor Gamblin
2020-07-11 3:19 ` [meta-python][PATCH 4/5] python3-gnupg: " akuster
2020-07-15 23:53 ` [oe] " Trevor Gamblin
2020-07-11 3:19 ` [meta-python][PATCH 5/5] python3-qrcode: add package akuster
2020-07-15 23:53 ` [oe] " Trevor Gamblin
2020-07-15 23:52 ` [oe] [meta-python][PATCH 1/5] python3-gmpy2: add new package Trevor Gamblin
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=20200711031932.5883-3-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-devel@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