Neil Bothwick <[EMAIL PROTECTED]> writes: > kde-base/kde is a meta package, it pulls in all the monolithic KDE > builds. If you are concerned about installation compile times, you should > not be trying to build the whole of KDE. Do you really need all of > kdegames, kdeedu and kdetoys to get your system running? Stick with > kde-base/kdebase or kde-base/kdebase-meta, you can cancel your current > emerge and merge one of these instead, then add the rest of what you want > once the system is running.
I'm confused here. (even more..) Before starting the compile: I ran a comparision of `emerge -v -p kde' and emerge -v -p kde-meta The last showed a much larger pile of dependancies than the former. So I ran the former. I've now canceled as suggested and running `emerge kde-base/kdebase' It only showed the main kde-3.4X as dependancy. But with all the screwups I've managed to get these kde packages installed: (And don't need several of them) kde-base/kdegraphics-3.4.1-r1 * kde-base/kdelibs-3.4.1-r1 * kde-base/kdebase-pam-6 * kde-base/kde-env-3-r4 * kde-base/arts-3.4.1-r2 * kde-base/kdebase-3.4.1-r1 * kde-base/kdeartwork-3.4.1 * kde-base/kdepim-3.4.1-r2 * kde-base/kdegames-3.4.1 * kde-base/kdeutils-3.4.1 * kde-base/kdenetwork-3.4.1-r1 * kde-base/kdeedu-3.4.1-r1 * -- gentoo-user@gentoo.org mailing list
