In the table that lists the packages not pulled in by kde-base/kdebase-startkde meta package, there are the following ones: - kcontrol - kicker - konqueror that they're actually pulled in by kdebase-startkde meta-package. You can check this running # emerge -ep kdebase-startkde I suggest to remove these entries from the table, changing also the Code Listing 2.3 accordingly. I also suggest to add an item to the list of suggested installation types, like this (please take my example with caution, my english is all but perfect :P ;-) ): * If you want a full-blown KDE installation, install kde-meta. This package will pull in all KDE applications as dependencies. * If you want a basic KDE installation, install kdebase-startkde. You can always install additional KDE applications when you want. + * If you want a basic KDE installation, with some almost necessary tool (like Graphical Login Manager and Console Emulator), install kdebase-meta There's another thing: in the Code Listing 3.2 it's suggested to install kdm with emerge "--noreplace" switch, but if the user does this operation, the first time he will run "emerge --depclean" the kde-base/kdm package will be marked for removal, because it's installed but not listed in the world file, and it isn't actually dependency of any package. I suggest to remove the "--noreplace" switch, adding a note that explain that the installation of this package is not required if the user has previously installed "kdebase-meta" or "kde-meta" packages.
I'm not sure what you mean by " If you want a basic KDE installation, with some almost necessary tool (like Graphical Login Manager and Console Emulator), install kdebase-meta" -- can you clarify please? Your English is a little tricky to figure out here. But I'll fix the other stuff at least.
I figured out what you meant -- kdebase-meta is a compromise between kdebase-startkde and kde-meta. I also took the time to rework the bit on hal/dbus, as those should also not be installed by --noreplace, but with --ask. They should have been pulled in already with the appropriate USE flags, hence giving the user the command to verify that they were installed. Fixed in CVS, thanks for reporting.
