Hi, Il 22/10/18 20:59, Andreas Beckmann ha scritto: > Just an idea, do not know if this can be implemented efficiently: > > If libboost-python1.62.0 provides pythonX.Y-libboost-python1.62.0 > and the consumers depend on pythonX.Y-libboost-python1.62.0 instead of > (or in addition to) libboost-python1.62.0, everything should be fine.
I see the problem, thanks for bringing this up. I agree with your solution: basically we let Boost.Python expose the Python versions it is compiled with, so that packages can depend on the right version. It seems reasonable. I would just change the provided package name, because calling something "pythonX.Y-name" seems to imply that there is an actual Python extension called "name" inside, which is not the case here. I would use something like "libboost-python1.62.0-pyXY". Also, I'll do the same for boost1.67, which would have the same problem. Thanks, Giovanni. -- Giovanni Mascellani <g.mascell...@gmail.com> Postdoc researcher - Université Libre de Bruxelles
signature.asc
Description: OpenPGP digital signature
