Re: [thud, warrior, zeus][meta-python] Conundrum: python-pycrypto and python-pycryptodome

[Adrian Bunk <bunk@stusta.de>]

On Wed, Dec 04, 2019 at 09:00:20PM -0800, Tim Orling wrote:
> 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?
>...

The minimal change for stable branches would be to add RCONFLICTS
on python{,3}-pycryptodome to python{,3}-pycrypto.

In a stable branch changing what users get installed is not really
worth it for a tiny bit of improved testing coverage.

Based on what you wrote, for master the best solution will likely 
include removing python{,3}-pycrypto.

cu
Adrian