The following error happens: Traceback (most recent call last): > File > "/var/tmp/portage/kde-base/kdeplasma-addons-4.2.0/work/kdeplasma-addons-4.2.0/applets/lancelot/tools/puck/puck.py", > line 25, in ? > from Modules.Layouts import * > File > "/var/tmp/portage/kde-base/kdeplasma-addons-4.2.0/work/kdeplasma-addons-4.2.0/applets/lancelot/tools/puck/Modules/Layouts/NodeLayout.py", > line 1 > from .. import LayoutHandlerManager > ^ > SyntaxError: invalid syntax > make[2]: *** [applets/lancelot/app/src/ui_LancelotWindowBase.h] Error 1 > make[1]: *** [applets/lancelot/app/src/CMakeFiles/lancelot-menu.dir/all] > Error 2 > make[1]: *** Waiting for unfinished jobs.... > Linking CXX shared module ../../lib/krunner_spellcheckrunner.so > [ 68%] Built target krunner_spellcheckrunner > make: *** [all] Error 2 > * > * ERROR: kde-base/kdeplasma-addons-4.2.0 failed. After upgrading to Python 2.5.2, package compiled successfully. I do not know the minimal Python version (above 2.4.4) that is required for the 'from .. import' syntax. Reproducible: Always Steps to Reproduce: This bug blocks emerging of KDE 4.2.0 on system with an out-of-the-box (gentoo) Python.
I doubt this can be supported. dev-lang/python-2.5.2-r7 has been stable for all arches since September 17, 2008. Adding python 2.5 as dependency to every last package in the tree that needs it would be a lot of work.
@Jeroen, I understand what you're saying, but: The latest Gentoo stage3 snapshot does _not_ contain a version good for this. Nowhere in the handbook (at least - the installation chapter), one is advised to put his system up 2 date immediately after installation. The result is, that, because of this package (and _only_ this package), someone who tries to install the full kde 4.2.0 on a brand new system, will fail. (OK, there are two more packages, that probably has the same problem, and those are 'marble' and 'plasma-workspace' - but they can be avoided by doing USE=-python on the packages that require them [see bug #256728] - I am not even sure the problem there is Python, but just now that I think of it...) So I am saying... for the sake of users simplicity, I am not asking to set this to every new python-depending package; Just those 3 that enables people to install a high-profile package like KDE 4.2.0. It really is ~1 minute of work, and it will probably save lots of 'users support' later :-) Thanks!
Now, stages are periodically auto-generated, and they contain the most recent stable package set for specified arch, so 'stage' argument is no longer valid. Besides, as you noted, users are *advised* to update their system just after their set up.
jer and reavertm made a good point, closing as wontfix
