I wouldn't acutally call this a bug. It's more of a question/request. The question is: Why is GTK 2.4 a requirement for Eclipse-SDK 2.1.3 series when it only requires GTK 2.2? REF: http://www.eclipse.org/eclipse/development/readme_eclipse_2_1_3.html#TargetOperatingEnvironments The request is: Baring some technical problem, please change to GTK 2.2. The 3.0 pre ebuilds don't have the GTK 2.4 requirement. So why would you require it on 2.1.3 builds. Just so you know why this is a problem, I currently run a stable system baring a few exception. GTK 2.4 hasn't been marked stable yet, and I don't seed the need to mark it so that I could. Also, I have emerged it with GTK 2.2.4 with no porblems that I can tell. I changed the ebuild's requirements. But when I emerge rsync, I have to change it again. This has become an anoyance. Reproducible: Always Steps to Reproduce:
I have a no idea. I have been away from the eclipse stuff for a few months, and was told that the deps needed to be updated, so I gave my consent. I'll get onto it. I also run this with gtk+-2.2 flawlessly, so I'll down-bump it after proper investigation.
In the meantime, 2.4 has been marked stable on most Gentoo archs, and it has the same SLOT as 2.2, which means everybody will upgrade it very soon anyways. If, for some reason, we find regressions going from 2.2 to 2.4, I'll reconsider down-bumping. I do naturally agree that it would be ideal to have proper testing done for 2.2 as well, but at the moment, I simply don't have the time. If you disagree, please reopen the bug with a rationale. I'm a reasonable, overworked guy;)
