i was recommended to use the ~amd64 keyword to get kde 3.4.2 but i got 3.5. While installing i got an error about missing files. "emerge kdebase-startkde" worked untill it reached kcontrol, then it said "Can't find library libkonq under /usr/kde/3.5/lib64/" . After a manual "emerge libkonq" it complained about a libkicker missing. So i also manually emerged kicker, and after that kcontrol (and kdebase-startkde) seems to install allright (so far, it's still going) So i think the emerge of kdebase-startkde just missed two dependencies, or failed to emerge them first (they were later in the list of "packages to install" for "emerge -p kdebase-startkde" Greetz, geert Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Expected Results: first emerge libkonq, and kicker, and then kcontrol (in the kdebase-startkde group)
> i was recommended to use the ~amd64 keyword to get kde 3.4.2 but i got 3.5. Do you mean that you unmasked it on purpose, or that you asked for 'kde' and got it? If the latter check your /etc/portage/package.unmask for relevant lines. Anyway, 3.5_alpha1 is very alpha, lots of ebuilds don't (always) compile and I don't even really want to get bugreports about it (other than obvious ebuild problems), because I'd rather be packaging 3.5_beta1. So please either wait for beta1 ebuilds or go back to the stable 3.4.2 if that's what you want. > So i think the emerge of kdebase-startkde just missed two dependencies, or > failed to emerge them first (they were later in the list of "packages to > install" for "emerge -p kdebase-startkde" You may have emerged the 3.5_alpha1 ebuilds as they were being committed, and some fixes went in after you started emerging...
