On Thu, Jun 14, 2018 at 1:57 AM, Petter Reinholdtsen <p...@hungry.com>
wrote:
[Andres Salomon]
I modified the package to provide/conflict with python-crypto, and
that
seems to work. I didn't test upgrade paths, though.
Would it be better to introduce a extra set of Crypto compatible
packages?
It would allow those packages using the current namespace to keep
working
without changes, and allow them to use the "compat" packages if they
want to.
It sounds like that's the intent upstream, according to
(https://www.pycryptodome.org/en/latest/src/introduction.html)?
I think in the ideal scenario, there's a python3-pycryptodome binary
package
that conflicts/provides python3-crypto and uses the Crypto namespace,
and a python3-pycryptodomex binary package that uses the Cryptodome
namespace. Just the latter would probably be fine, though.
