Hi Jakob,
We have a test in the easyconfigs test suite that catches conflicts like
this, so you shouldn't ever run into on.
But taking into account build dependencies is important of course. :)
On 16/12/2020 14:40, Jakob Schiøtz wrote:
Hi again,
I realize now that Python 2.7 is only a build dependency of OpenPGM, which
prevents it from being a real conflict. But still unfortunate to have to
install an obsolete python version to build it.
I don't know from the top of my head whether OpenPGM strictly requires
Python 2 as a build dependency, but it's possible.
We certainly have other cases where that's the case, Qt5 is one (see
https://github.com/easybuilders/easybuild-easyconfigs/pull/11386 for
example).
regards,
Kenneth
Best regards
Jakob
--
Jakob Schiøtz, professor, Ph.D.
Department of Physics
Technical University of Denmark
DK-2800 Kongens Lyngby, Denmark
http://www.fysik.dtu.dk/~schiotz/
On 16 Dec 2020, at 14.31, Jakob Schiøtz <schi...@fysik.dtu.dk> wrote:
Hi EasyBuilders,
It looks like there is a potential package conflict when building
IPython-7.18.1-GCCcore-10.2.0.eb
The package depends on Python-3.8.6-GCCcore-10.2.0.eb and
ZeroMQ-4.3.3-GCCcore-10.2.0.eb (fine)
But ZeroMQ depends on OpenPGM-5.2.122-GCCcore-10.2.0.eb which in turn depends
on Python-2.7.18-GCCcore-10.2.0.eb
Will this not cause two conflicting Python packages to be loaded (conflicting
as in the binary python will be the one last loaded, and perhaps PYTHONPATH
will also be a mess)?
Best regards
Jakob
--
Jakob Schiøtz, professor, Ph.D.
Department of Physics
Technical University of Denmark
DK-2800 Kongens Lyngby, Denmark
http://www.fysik.dtu.dk/~schiotz/
