If you are missing the Krusader Filetransfer/Progress Dialogs, then emerge at least kde-base/kuiserver. This is an unresolved dependency to krusader-2.4.0-r1.ebuild and occurs if you do not emerge the meta-packages: kdebase-meta and/or kdebase-runtime-meta (or any other ebuild wich may solve this dependency) Maybe kde-base/kuiserver has to be added to the RDEPEND-list "$(add_kdebase_dep kuiserver)" in the future Eventually this should be done with kde-base/kdebase-kioslaves and a new USE-flag e.g. "sftp" or "ssh", too. my emerged ebuilds from kde-base and kde-misc are [I] kde-base/kate [I] kde-base/katepart [I] kde-base/kde-env [I] kde-base/kde-l10n [I] kde-base/kde-wallpapers [I] kde-base/kdebase-data [I] kde-base/kdebase-kioslaves [I] kde-base/kdelibs [I] kde-base/kdesu [I] kde-base/kdialog [I] kde-base/keditbookmarks [I] kde-base/kompare [I] kde-base/kuiserver [I] kde-base/libkonq [I] kde-base/okular [I] kde-base/oxygen-icons [I] kde-misc/kdiff3 [I] kde-misc/krename [I] kde-misc/krusader [I] kde-misc/polkit-kde-kcmodules
Hm, interesting. I did some digging, and found the following: http://docs.kde.org/development/en/extragear-utils/krusader/faq.html#idp45493408 It basically says that you don't _have_ to have most kde stuff beyond kdelibs for krusader to work, but for it to be functional you need assorted other libs and packages, and it's not terribly clear what functionality is given by what package. Unfortunately, these aren't build-deps, or even run-deps; they're optional dependencies with no linking involved, so they shouldn't even be in RDEPEND. I think a post-install message would be appropriate here, but there are so many different components that are plug-in like this (kioslaves, progress bars, jpeg support, id3 info...) that this would be a lot of packages. For now, I'm going to shoot upstream an email and ask what packages exactly provide what service, then we can sort this out.
This is invalid bug. We state by eclass that if you intend to use any of the kde features you need to merge the runtime-meta. We would add this dep everywhere but quite few people were b**ching that it just pulls more packages when they just need some thing from kde and don't care about consequences. ewarn "WARNING! Your system configuration contains neither \"kde-base/kdebase-runtime-meta\"" ewarn "nor \"kde-base/kdebase-startkde\". You need one of above." ewarn "With this setting you are unsupported by KDE team." ewarn "All missing features you report for misc packages will be probably ignored or closed as INVALID."
(In reply to comment #1) > Hm, interesting. I did some digging, and found the following: > http://docs.kde.org/development/en/extragear-utils/krusader/faq. > html#idp45493408 > It basically says that you don't _have_ to have most kde stuff beyond > kdelibs for krusader to work, but for it to be functional you need assorted > other libs and packages, and it's not terribly clear what functionality is > given by what package. Unfortunately, these aren't build-deps, or even > run-deps; they're optional dependencies with no linking involved, so they > shouldn't even be in RDEPEND. I think a post-install message would be > appropriate here, but there are so many different components that are > plug-in like this (kioslaves, progress bars, jpeg support, id3 info...) that > this would be a lot of packages. For now, I'm going to shoot upstream an > email and ask what packages exactly provide what service, then we can sort > this out. thanks for your reply, a feature dependency list would be a nice thing. And yes, it may not be a bug, krusader compiles and works fine. But having no file-transfer progress dialogs was quite annoying for several months now. And I just had the time to figure out which package solves the problem.
(In reply to comment #2) > This is invalid bug. > > We state by eclass that if you intend to use any of the kde features you > need to merge the runtime-meta. > > We would add this dep everywhere but quite few people were b**ching that it > just pulls more packages when they just need some thing from kde and don't > care about consequences. > > ewarn "WARNING! Your system configuration contains neither > \"kde-base/kdebase-runtime-meta\"" > ewarn "nor \"kde-base/kdebase-startkde\". You need one of above." > ewarn "With this setting you are unsupported by KDE team." > ewarn "All missing features you report for misc packages will be probably > ignored or closed as INVALID." Absolutely right. Do not complain if you have not emerged the META packages. I am using XFCE, so I have not noticed that some progress dialogs are now handled by the K Desktop Environment. That is why I tried to figure out how I can get these dialogs back - I have copied data without status for some time now.
