On Tue, Mar 10, 2020 at 12:56 PM Vesa Jääskeläinen <dach...@gmail.com> wrote:
> Hi, > > Actually no. > > pythonX-cryptodome has need to conflict with pythonX-crypto. > > But python3-cryptodomex can coexists with either one of those as they > have own namespace. > That is probably what I am remembering, since I had to fix that exact issue on meta-python2. > Some software need to unfortunately have both python3-cryptodome (brings > python3-crypto "API emulation") and python3-cryptodomex installed in > order to function. > We (all of us ;) should look for recipes that have legacy RDEPENDS on python3-crypto or python3-cryptodome , when in fact they could use the cleaner solution of python3-cryptodomex. Commits I made in meta-python2 might help. Thank you for digging deeper and capturing the state of things. > Thanks, > Vesa Jääskeläinen > > On 10.3.2020 7.50, Tim Orling wrote: > > This probably should have an RCONFLICTS with python3-cryptodme (and maybe > > even python3-crypto). > > > > These three packages step all over each other with same functionality... > > > > On Mon, Mar 9, 2020 at 7:50 PM Scott Branden via Openembedded-devel < > > openembedded-devel@lists.openembedded.org> wrote: > > > >> From: Rajesh Ravi <rajesh.r...@broadcom.com> > >> > >> Add python3-pycryptodomex 3.9.4 recipe needed to build > >> such components as optee 3.8.0. > >> > >> Signed-off-by: Rajesh Ravi <rajesh.r...@broadcom.com> > >> Signed-off-by: Scott Branden <scott.bran...@broadcom.com> > >> --- > >> .../python/python3-pycryptodomex_3.9.4.bb | 30 > +++++++++++++++++++ > >> 1 file changed, 30 insertions(+) > >> create mode 100644 meta-python/recipes-devtools/python/ > >> python3-pycryptodomex_3.9.4.bb > >> > >> diff --git a/meta-python/recipes-devtools/python/ > >> python3-pycryptodomex_3.9.4.bb b/meta-python/recipes-devtools/python/ > >> python3-pycryptodomex_3.9.4.bb > >> new file mode 100644 > >> index 000000000..be6b10f3f > >> --- /dev/null > >> +++ b/meta-python/recipes-devtools/python/ > python3-pycryptodomex_3.9.4.bb > >> @@ -0,0 +1,30 @@ > >> +SUMMARY = "Cryptographic library for Python" > >> +DESCRIPTION = "PyCryptodome is a self-contained Python package of > >> low-level\ > >> + cryptographic primitives." > >> +HOMEPAGE = "http://www.pycryptodome.org" > >> +LICENSE = "PD & BSD-2-Clause" > >> +LIC_FILES_CHKSUM = > >> "file://LICENSE.rst;md5=6dc0e2a13d2f25d6f123c434b761faba" > >> + > >> +SRC_URI[md5sum] = "46ba513d95b6e323734074d960a7d57b" > >> +SRC_URI[sha256sum] = > >> "22d970cee5c096b9123415e183ae03702b2cd4d3ba3f0ced25c4e1aba3967167" > >> + > >> +inherit pypi > >> +inherit setuptools3 > >> + > >> +RDEPENDS_${PN} += " \ > >> + ${PYTHON_PN}-io \ > >> + ${PYTHON_PN}-math \ > >> +" > >> + > >> +RDEPENDS_${PN}-tests += " \ > >> + ${PYTHON_PN}-unittest \ > >> +" > >> + > >> +PACKAGES =+ "${PN}-tests" > >> + > >> +FILES_${PN}-tests += " \ > >> + ${PYTHON_SITEPACKAGES_DIR}/Cryptodome/SelfTest/ \ > >> + ${PYTHON_SITEPACKAGES_DIR}/Cryptodome/SelfTest/__pycache__/ \ > >> +" > >> + > >> +BBCLASSEXTEND = "native nativesdk" > >> -- > >> 2.17.1 > >> > >> -- > >> _______________________________________________ > >> Openembedded-devel mailing list > >> Openembedded-devel@lists.openembedded.org > >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel > >> > -- > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel