| 1 |
On Saturday 20 December 2008 08:27:40 Nikos Chantziaras wrote: |
| 2 |
> emerge -av --depclean: |
| 3 |
> |
| 4 |
> kde-base/kopete |
| 5 |
> |
| 6 |
> selected: 3.5.10 |
| 7 |
> |
| 8 |
> protected: none |
| 9 |
> |
| 10 |
> omitted: 4.1.3 |
| 11 |
> |
| 12 |
> |
| 13 |
> kde-base/kget |
| 14 |
> selected: 3.5.10 |
| 15 |
> protected: none |
| 16 |
> omitted: 4.1.3 |
| 17 |
> |
| 18 |
> kde-base/kmenuedit |
| 19 |
> selected: 3.5.10 |
| 20 |
> protected: none |
| 21 |
> omitted: 4.1.3 |
| 22 |
> |
| 23 |
> The list goes on. All those packages are in my world file. This only |
| 24 |
> started happening after installing KDE 4.1.3. Another nice effect of |
| 25 |
> not putting KDE4 in new portage trees but rather mixing them with KDE3? |
| 26 |
> What can I do? |
| 27 |
|
| 28 |
You can start by giving the relevant information, like what exactly related to |
| 29 |
kde is in world?. Chances are you only have KDE there, and emerge will |
| 30 |
probably want to nuke all but the latest SLOT. Common problems with KDE: |
| 31 |
|
| 32 |
Put 'kdeprefix' in USE and rebuild |
| 33 |
Put KDE:3.5 in world and recheck. |
| 34 |
|
| 35 |
This last one often needs to be redone recursively to get everything in world |
| 36 |
that needs to be there. I've heard that autounmask helps with this |
| 37 |
|
| 38 |
-- |
| 39 |
alan dot mckinnon at gmail dot com |
Archives