I don't think it is necessary for the kdevelop ebuild to inherit all dependencies from kde-base. I emerged each ebuild from kde-base separately to avoid installing things like lynx or tetex. When I emerge kdevelop I will have them foisted on me. Do I really need these for a C/C++ development package?
We (me, Seemant et al) had a discussion about this and the conclusion is more or less that the default behaviour remains, for now, the same since the great majority of users are happy that way. We do however propose to add, after the current freeze period and when new features are again added to potrage, a new global use flag that would make packages depend either on just the things they absolutely need, or on everything that they can use. You could then disable it and get what you want, in kdevelop as well as other ebuilds.
Of course, 'minor' or 'local' use variables wuold be even more fun...
All bugs now live at kde@gentoo.org. I'll return to issues like this after kde 3.1 and gentoo 1.4 have been released and the stable tree is unfrozen.
OK, I've removed all optional runtime deps, instead printing a pkg_postinst() list of them with short descriptions. I trimmed down the DEPEND list to necessities too, and made jdk and python depend on the java and python use flags. Should be ok now. This is in kdevelop-3.0_alpha3.ebuild. kdevelop 2.x is unmaintained upstream (sorta), and I don't want really to mess with it either... Hope that's satisfactory.
