Following targets for moves... kde-base/kicker-applets kde-base/kdeaddons-kfile-plugins kde-base/kdebase-data kde-base/kdewebdev kde-base/kdenetwork kde-base/kate-plugins kde-base/noatun-plugins kde-base/ksvg kde-base/konq-plugins are listed for collapsing a *lot* of packages into. If they're alternatives (kernel sources fex, seperated pkgs based on arch), one can slide by; regardless if upstream has collapsed pkgs together for a certain version, collapsing the existing pkgs doesn't really fly. Think about it- does an existing kde-base/kdebase-i10n satisfy the the full kdebase-data requirements? Basically... if a new version merges it upstream, deps should abuse || () to rely on seperated components or the combined version (as you're doing already). The moves however, are uneeded and aren't particularly proper. That and we really need a better 'component' for bugs when it's screwwy meta tree stuff ;)
Closing, was resolved without bug being updated.
