Currently the kdevelop ebuild finishes with pkg_postinst() { einfo "kdevelop can use a wide range of apps for extra functionality. This is an almost" einfo "complete list. All these packages can be emerged after kdevelop." einfo einfo "kde-base/kdebase: (RECOMMENDED) embed konsole kpart in kdevelop ide" einfo "dev-util/kdbg: (RECOMMENDED) kde frontend to gdb" einfo "dev-util/valgrind: (RECOMMENDED) integrates valgrind (memory debugger) commands" einfo "kde-base/kompare: (RECOMMENDED) show differences between files" einfo "dev-java/ant: support projects using the ant build tool" einfo "dev-util/ctags: faster and more powerful code browsing logic" einfo "app-doc/doxygen: generate KDE-style documentation for your project" einfo "www-misc/htdig: index and search your project's documentation" einfo "app-arch/rpm: support creating RPMs of your project" einfo "app-emulation/visualboyadvance: create and run projects for this gameboy" einfo einfo "Support for GNU-style make, tmake, qmake is included." einfo "Support for using clearcase, perforce and subversion" einfo "as version control systems is optional." } I would find it useful if there were some extra USE flags (something like kdev_kdbg, kdev_valgrind etc) to make kdevelop depend on these additional useful programs.
Use flags are not there for adding dependencies that don't affect the emerge result in any way. Adding such use flags is not appreciated by our QA at all, since such stuff obviously is not a dependency.
As Jakub said. They are neither depend nor rdepend, they are recognised at build time.
As Jakub said. They are neither depend nor rdepend, they are recognised at run time (little thinko).
surely they are runtime dependencies *if* you want to use that particular plugin/feature from within kdevelop - OK, the program will start without them, but you can't do what you want to do.
