On Monday, 12 June 2006 3:17, Kevin O'Gorman wrote:
> Once again... portage is mad at me, I guess... unless I'm not alone
> kdepim is required by KDE:
> treat ~ # equery --nocolor depends kdepim-3.5.2-r2
> [ Searching for packages depending on kdepim-3.5.2-r2... ]
> kde-base/kde-3.5.2
> kde-base/kdeaddons-3.5.2-r1
> treat ~ #
> BUT is blocked by other pieces of KDE
> [blocks B ] =kde-base/libkpgp- 3.5* (is blocking kde-base/kdepim-
> 3.5.2-r2)
> [blocks B ] =kde-base/libkmime-3.5* (is blocking kde-base/kdepim-
> 3.5.2-r2)
> [blocks B ] =kde-base/libkpimidentities-3.5* (is blocking
> kde-base/kdepim-3.5.2-r2)
> [blocks B ] =kde-base/kalarm-3.5* (is blocking kde-base/kdepim-
> 3.5.2-r2)
> [blocks B ] =kde-base/libkdepim-3.5* (is blocking kde-base/kdepim-
> 3.5.2-r2)
> [blocks B ] =kde-base/ktnef-3.5* (is blocking kde-base/kdepim-
> 3.5.2-r2)
> [blocks B ] =kde-base/certmanager-3.5* (is blocking kde-base/kdepim-
> 3.5.2-r2)
> [blocks B ] =kde-base/libkdenetwork- 3.5* (is blocking
> kde-base/kdepim-3.5.2-r2)
> [blocks B ] =kde-base/libkcal-3.5* (is blocking kde-base/kdepim-
> 3.5.2-r2)
>
> I find it especially charming that libkdepim is blocking kdepim, both being
> of the 3.5 flavor.
> Can anyone tell me where to turn?
You can't mix and match monolithic and split ebuilds. kdepim-meta is the one
you're after.
That sounds interesting, but I have no idea what to do about it. I think once
upon a time, when I was first installing gentoo, I opted for KDE. I haven't done
a thing about it since KDE 3.2. Now all of a sudden I've got this conflict.
What do I need to change?
++ kevinb
--
Kevin O'Gorman, PhD
