Recently the ebuild for cmake-2.6.2 has been changed from EAPI 1 to 2. With this change, an "emerge world" would downgrade cmake to 2.4.something on an otherwise stable system. Why did you do that change? I couldn't find a bug clarifying the resoning behind this. This is unacceptable for me, since I need cmake 2.6 for our own development, but I also need a stable system which restrains me from upgrading to an unstable sys-apps/portage.
Well, cmake 2.6.2 IS still in unstable and there EAPI=2 happens often. What's more, AFAIK recent strange moves of the portage author/maintainer are an attempt to create and push sys-apps/portage-2.1.6 into stable (and this one will support EAPI=2).
Hi rej, i am part of kde team so no need to cc me additionaly. I am sorry i broke the cmake for you but we were discussing that and the ebuild needed few updates so i did them now when it was on the talk then forget about them. Actualy i just updated the current ebuild so you should have cmake-2.6.2 already and even without eapi2. I wont revert the update for the few days until eapi2 is in the tree with portage 2.1.6 stable. Please consider testing 2.1.6 it already should not harm kittens since we kde guys test it since 2.2_rcX because we needed it and no big issues were around. Closing as wontfix. NOTE: you can use viewcvs.py and grab old one if you really really dont want to update the portage.
(In reply to comment #2) > Hi rej, Hi > i am part of kde team so no need to cc me additionaly. I didn't. Stephan Springer did...
Yes, that was me - I took your id from the ChangeLog. Thanks for the hints. I think I'll wait till portage 2.1.6 goes stable. For the meantime I've made a local overlay with the old ebuild now.
