python-pycrypto [1] is rather old and un-maintained [2]. python-pycryptodome [3] is more modern and is basically a drop in replacement. However, the two cannot be installed at the same time. Instead, one would install python-pycryptodomex which does not conflict with the paths of python-pycrypto [4].
In an effort to enable packagegroup-meta-python [5] and meta-python-image [6], one runs into the existing python-pycrypto and python-pycryptodome recipes attempting to install the same files to the same locations (no surprise, they are providing the same libraries). For the stable branches, should we rename python-pycryptodome to python-cryptodomex and PROVIDES python-pycryptodome? [1] https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python-pycrypto_2.6.1.bb?h=zeus [2] https://github.com/dlitz/pycrypto/issues/285 [3] https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-devtools/python/python-pycryptodome_3.4.11.bb?h=zeus [4] https://stackoverflow.com/questions/48155294/what-is-pycryptodomex-and-how-does-it-differ-from-pycryptodome [5] https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-core/packagegroups/packagegroup-meta-python.bb?h=zeus#n21 [6] https://git.openembedded.org/meta-openembedded/tree/meta-python/recipes-core/images/meta-python-image.bb?h=zeus -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
