This breaks any Qt5 apps that use PyQt5 and import the PyQt5.sip module. dev-python/PyQt5-sip: builds/installs a broken PyQt5.sip module, files collide with package below (note this pkg provides nothing except a broken module). dev-python/sip: correctly builds a working PyQt5.sip but only if the configure arg is added to the ebuild (the module files collide with the above) dev-python/PyQt5: rdeps on dev-python/PyQt5-sip, deps on dev-python/sip. From an end-user perspective, ie, someone who needs to build/install a working sip module for a PyQt5 application, there is no reason for the dev-python/PyQt5-sip package unless it actually works out-of-the-box. The workaround for us is something like: 1. modify dev-python/PyQt5-5.12.2 to remove depends on PyQt5-sip package 2. modify dev-python/sip-4.19.17 and add configure arg: $(usex pyqt5 '--sip-module=PyQt5.sip' '') re-emerge the above and remove dev-python/PyQt5-sip package.
(In reply to Steve Arnold from comment #0) > This breaks any Qt5 apps that use PyQt5 and import the PyQt5.sip module. Can you be more specific? What breakage are you seeing? Please post the exact error(s). > dev-python/PyQt5-sip: builds/installs a broken PyQt5.sip module, files > collide with package below (note this pkg provides nothing except a broken > module). Broken how? Collides with what? dev-python/sip never installed a PyQt5.sip module so I'm confused. > dev-python/sip: correctly builds a working PyQt5.sip but only if the > configure arg is added to the ebuild Which is exactly what dev-python/PyQt5-sip does... > 1. modify dev-python/PyQt5-5.12.2 to remove depends on PyQt5-sip package > 2. modify dev-python/sip-4.19.17 and add configure arg: > > $(usex pyqt5 '--sip-module=PyQt5.sip' '') > > re-emerge the above and remove dev-python/PyQt5-sip package. The reason upstream invented "private" sip modules and PyQt5-sip is to allow different bindings modules to depend on different versions of the sip module, so that incompatibilities (and updates in general) of the sip module can be dealt with on a per application (or library) basis. What you're suggesting completely defeats the purpose.
Possibly related: bug 689882, comment 3
Hard to know, given that the reporter didn't provide any details.
(In reply to Davide Pesavento from comment #3) > Hard to know, given that the reporter didn't provide any details. I had serious issues to compile dev-python/sip-4.19.17, dev-python/PyQt5-sip-4.19.17, and dev-python/PyQt5-5.12.2, but finally it worked. After running emerge -v1 --keep-going $(find /usr/lib*/python3* -name '*cpython-3[0-9]*.so') /usr/include/python3.6m/ the problem went away. Sorry for not being more specific, but i simply can't :-/ But i still have the problem described in bug 689574.
