akregator (rss-reader for kde) is two times in portage, at net-www/akregator (old version) and kde-base/akregator (new version, part of kde 3.4).
For completeness, the same holds for kopete quanta kfilereplace kimagemapeditor kitchensync don't know exactly what to do about them, though...
They should persist as long as we support <kde-3.4. But there should be mutual blockers in all relevant packages.
all, except akregator, are part of kde-3.3 too, what about them?
We still have kde 3.2 in the tree and if we did not forgot any blockers, the kde 3.3 ebuild and standalone apps should block each other. The list is a bit longer e.g. I remember kgamma. Also no one cares for the quanta ebuild. I for one think, at least kopete and quanta should be removed now. Most of the others, when we drop kde 3.2 support.
I agree with Carsten. ebuilds for apps in kde 3.3 can be removed now, all the others can be removed when a kde 3.4 is unmasked. Move instructions should be added.
Heh, Dan, I wrote 3.2, since we still suport it. On the other hand a cleanup of this stuff and forcing everyone, who wants to use these applications, to install KDE 3.3 may be in order.
Closing, net-www/akregator will stay in the tree for kde-3.3 users, and all other duplicates were removed.
The following three packages survived the cleanup: ksambaplugin kolourpaint kmousetool ok to remove them? (with entries in updates/1Q-2005) net-misc/ksambaplugin -> kde-base/kdenetwork media-gfx/kolourpaint -> kde-base/kdegraphics x11-misc/kmousetool -> kde-base/kdeaccessibility
removed from portage.
Isn't it possible to make meta-ebuilds from the standalone ebuilds that depend on the ones in kde-base (or the other way around). That way users will never have problems with packages that block each other.
