Sorry to throw even more bugs at you: >>> Unpacking parts of kdebase-3.5.2.tar.bz2 to /var/tmp/portage/kcontrol-3.5.2/work Symlinking library libkonq under /usr/kde/3.5/lib/ in source dir !!! ERROR: kde-base/kcontrol-3.5.2 failed. Call stack: ebuild.sh, line 1546: Called dyn_unpack ebuild.sh, line 708: Called src_unpack ebuild.sh, line 1255: Called kde-meta_src_unpack kde-meta.eclass, line 332: Called die !!! Can't find library libkicker under /usr/kde/3.5/lib/ !!! If you need support, post the topmost build error, and the call stack if relevant.
Can't reproduce: - kcontrol already dependes on kicker - there is no libkicker anywhere
libkicker refers to libkicker main which is pulled by kicker. kicker is already a dependency to the ebuild, so it makes no sense that the ebuild complains about it.
I can't reproduce it, however I am intrigued on how this happened. I need to know the output of `emerge -pv kcontrol` for you and that you check if kde-base/kicker is already installed when that error message is shown. Summary: Need additional details :)
