| 1 |
Willie Wong wrote: |
| 2 |
> On Mon, Dec 22, 2008 at 02:18:27AM +0200, Penguin Lover Nikos Chantziaras squawked: |
| 3 |
>> Nikos Chantziaras wrote: |
| 4 |
>>> kde-base/kate |
| 5 |
>>> kde-base/kdebase-startkde |
| 6 |
>>> kde-base/ksmserver |
| 7 |
>>> These were dependencies and therefore were not in my world file. If they |
| 8 |
>>> get unmerge, things will break. KDevelop will break without Kate, and KDE |
| 9 |
>>> 3.5 itself will break without the other two. :P |
| 10 |
>> OK, now I'm really curious; turns out they are NOT dependencies :P I just |
| 11 |
>> checked with equery and nothing depends on them. Is that normal? I mean, |
| 12 |
>> startkde for example is crucial to even start KDE 3 and it's not a |
| 13 |
>> dependency? |
| 14 |
> |
| 15 |
> Hum, that is bizarre. I just tried emerge -pvt kde-meta, and it shows |
| 16 |
> that kde-meta depends on kdebase-meta depends on kdebase-startkde |
| 17 |
> (all version 3.5.9) |
| 18 |
> |
| 19 |
> Checking all the ebuilds currently in the tree (versions 3.5.9, |
| 20 |
> 3.5.10, 4.1.2 and 4.1.3), shows that all versions of kdebase-meta |
| 21 |
> depend on their corresponding versions of kdebase-startkde (they all |
| 22 |
> contain the line |
| 23 |
> |
| 24 |
> >=kde-base/kdebase-startkde-${PV}:${SLOT} |
| 25 |
> |
| 26 |
> which picks the right slot). So something is probably broken on your |
| 27 |
> system. Check the contents of the various ebuilds for the versions you |
| 28 |
> installed to see what's wrong. |
| 29 |
|
| 30 |
I'm not using -meta packages. Many packages they pulled in was stuff I |
| 31 |
don't wanted (like PIM). I emerged KDE packages one-by-one and went |
| 32 |
with what got pulled in as dependencies. |
Archives