A long outstanding issue in the portage tree is the version numbering convention of qscintilla. 1.6 is the most up to date version. 1.65 is identical to 1.6, but this is not the correct way to identify the version. The eric ebuilds identify the latest release that uses the correct naming convention by masking <qscintilla-1.6, but <qscintilla-1.54 is more appropriate. This is the change I am requesting. Most appropriate would be to clean all versions of qscintilla that are improperly named out of the portage tree, versions 1.54 and greater. Reproducible: Always Steps to Reproduce: 1. 2. 3.
*** This bug has been marked as a duplicate of 83813 ***
bug 83813 does not address the issue reported in this bug report, which is that the eric ebuilds mask the most recent qscintilla (either 1.6 or 1.65), which is required by PyQt-3.15 in order to build the qtext module. I guess my last comment in the original post was misleading. The eric ebuilds need modification.
(In reply to comment #2) > bug 83813 does not address the issue reported in this bug report, which is that > the eric ebuilds mask the most recent qscintilla (either 1.6 or 1.65), which is > required by PyQt-3.15 in order to build the qtext module. Of course it does address it, read that bug and comments in there more carefully. This needs to be resolved *properly*, instead of messing with dependencies like <qscintilla-1.6 or <qscintilla-1.54, which are broken by design anyway and there's no need for them as well once the versioning is fixed. It's qscintilla versioning scheme that's broken in the first place.
I've read the bug report, I posted a number of the comments there. How about this: qscintilla should be removed from the eric dep list altogether. eric depends on PyQt, PyQt depends on qscintilla.
(In reply to comment #4) > How about this: qscintilla should be removed from the eric dep list altogether. > eric depends on PyQt, PyQt depends on qscintilla. Did so, for future (quick) reverse dependency checking implicit deps are not favourable, though. On the other hand this case will depend on the correct QScintilla/PyQt combination anyways. Regarding the change in version QScintilla version numbering see bug 117246
