1 |
The reason it blocks is because you have other packages installed that depend |
2 |
on kde-base/kdebase. For example: kde-base/kdepim and kde-base/kdenetwork |
3 |
These are all part of the monolithic packages. |
4 |
|
5 |
First you'll have to make a choice between monolithic (grouped) and segregated |
6 |
(split). Once you've made your choice you should unmerge all kde packages |
7 |
that belong to the type you don't want. You can recognize monolithic packages |
8 |
as they have a "kde-base/<packagename>-meta" replacement which use the split |
9 |
packages. |
10 |
|
11 |
On Tuesday 01 November 2005 23:59, Hamish Marson wrote: |
12 |
> Sebastian Redl wrote: |
13 |
> > Hamish Marson wrote: |
14 |
> >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 |
15 |
> >> |
16 |
> >> I have a problem with emerging kde... ever since going to 2005.0 |
17 |
> >> I get |
18 |
> > |
19 |
> > It seems that you have a few packages from the split ebuild version |
20 |
> > of KDE installed. Since the grouped ebuilds and the split ebuilds |
21 |
> > contain the same programs, they block each other. |
22 |
> > |
23 |
> > I recommed completely cleaning out everything from kde-base and |
24 |
> > starting anew then. (I'd install the split ebuilds then, but it's |
25 |
> > your call.) |
26 |
> |
27 |
> Yeah... I thought I'd already been that route once already... It would |
28 |
> be nice to know why the system thinks it has kde-base (Grouped?) |
29 |
> installed, when trying to unmerge it says that it isn't installed at |
30 |
> all... |
31 |
-- |
32 |
gentoo-amd64@g.o mailing list |