PyQt is also provided by kdebindings (> 3.3.0) and if kdebindings are installed dev-util/eric should not require dev-python/PyQt. gentux darkssj # etcat -v kdebindings [ Results for search key : kdebindings ] [ Candidate applications found : 5 ] Only printing found installed programs. * kde-base/kdebindings : [ ] 3.1.5 (3.1) [ ] 3.2.0 (3.2) [ ~ ] 3.2.2 (3.2) [ ~ ] 3.2.3 (3.2) [ I] 3.3.0 (3.3) gentux darkssj # emerge eric -pvt These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [ebuild N ] dev-util/eric-3.5.0 -idl 1,382 kB [ebuild N ] dev-python/PyQt-3.13 -doc 0 kB [ebuild N ] dev-python/qscintilla-1.61 -doc 0 kB [ebuild N ] dev-python/sip-4.1.1 -doc 0 kB Total size of downloads: 1,382 kB Reproducible: Always Steps to Reproduce: 1. emerge kdebindings (> 3.3.0) 2. emerge eric -p
It is only provided, if kdebindings is installed w/ python use flag enabled. Right now we have no proper way to catch such a second level dependency. Also there're some other kde related changes pending. I can't do much about it for now.
Created attachment 43582 [details] leo-4.2.ebuild
Created attachment 43583 [details] leoConfig.py.patch
Wrong bug, ignore attachments, sorry.
Actually now there's a way to check USE flags. The problem is how to DEPEND on one or the other.
The current kdebindings/python/README.copy states: ================ This directory holds a copy of: * SIP 4.1.1, Python binding generator for C++ from Riverbank Computing. http://www.riverbankcomputing.co.uk/sip/index.php Published under basically the Python License. (=GPL compatible) * PyQt (PyQt-x11-gpl-3.13), Python bindings for Qt from Riverbank Computing. http://www.riverbankcomputing.co.uk/pyqt/index.php Published under the GPL. * PyKDE 3.11.3, Python bindings for KDE from Riverbank Computing. http://www.riverbankcomputing.co.uk/pykde/index.php Published under the GPL. This set of software has been patched to work 'out of the box' with this version of KDE. ================== I'm not sure what the patches referred to are, but they can't be very big... In any case, kde-base/kdebindings is being replaced by kde-base/kdebindings-meta and the attached split ebuilds - i.e. separate ebuilds for separate bindings. With kdebindings removed, no ebuild in kde-base provides pyqt/pykde/sip anymore. (And I'll be happy for python@ to stay in charge of the python bindings :-)
Dan: There's Bug 76986 and I'm more or less waiting for the next upstream release (shouldn't take that long) to perform a couple of changes. Also I don't see a reason to have sip and PyQt twice in the tree. Integrating PyKDE from kdebindings as normal revision bump in the PyKDE package should suffice.
kde-base/pykde in cvs, depending on dev-python/PyQt