Because within the unmodified sources it is only watched out for Pyhton Version < 2.6 there will the scripting Modules never be build. So on Systems where only >=Python-2.6 is installed Scripting is disabled. Reproducible: Always Steps to Reproduce: 1.emerge scribus 2. 3. Actual Results: No scripting is enabled. Expected Results: There should be a Menu for Scripts an with scripts. If i download the sources for 1.3.5.1 an compile manually Python is found and the Scripting is enabled.
Created attachment 215100 [details] Exemplary build.log of 1.3.3.11 Proofs search for Versions of Python just < 2.6
As for 1.3.3.11, it's another "success" of KDevelop. Attach a build log of one of the cmake versions. And anyway, as all of the qt:3 depending packages will get masked/removed within a couple months, is this a problem ?
OK, should have checked the facts first - 1.3.5 is Qt4. As such this is an urgent version bump (urgent due to upcoming masking/removal of qt:3)
I think this one is not a question of qt-version. The configure-script has to be run with --enable-scripter2=yes and the part where the watch-out-for-python-versions has to be changed to look out for 2.6. Then compiling starts and tries to build the scripting parts also. Unfortunately there is an error arising while compiling because of code differences in between python version <2.6 and 2.6. This might be the reason why the configure-script is only looking out for Versions <2.6 . This should be fixed upstream but - why spending work on old stuff. So as workaround one should install 2.5 in parallel because the big changes in the qt-tree (and probably also python-3-tree) it's not worse spending time into this. Users will have to change in a while and all mindpower should watch out the future problems. And it is already proofed that 1.3.5.1 is compiling and running -at least on amd64- although it starts crashing a bit again like older version with "signal #11".
