On Monday 29 January 2007 13:03:28 Duncan wrote:
> While I knew that world doesn't contain slots
> or versions, I thought (and believe it works that way in ~portage, but it
> may not have reached stable yet, and I could be wrong) that unmerging the
> metapackage would then release the dependency on the other stuff in that
> slot.  For KDE monolithics, for instance, I believe(d) that while
> old kdelibs won't be unmerged immediately as it isdepended on by
> kdebase which is depended on by (among others) kdegraphics, without the
> old kde-3.4.x, kdegraphics-3.4.x would be trimmed by --depclean, and once
> all the other kdewhatever-3.4.x packages had been trimmed, then
> kdebase-3.4.x could be trimmed, and then kdelibs-3.4.x

Nope. And it's not going to change anytime soon. A safer --prune, however, 
does have a good chance of going into portage 2.1.3 (to fix bug #151653).

> However, I'm using the split packages, not the monolithics, and don't have
> kde-meta merged as I don't need all the split packages either.

Doesn't really make a difference. The most basic deps (arts and kdelibs) don't 
differ at all. The problem with using kde as a test case is that kde-3.4 left 
the tree 4 months ago... ;)

-- 
Bo Andresen