On 26 Aug, Dale wrote: > Helmut Jarausch wrote: >> On 26 Aug, Dale wrote: >> >>> Helmut Jarausch wrote: >>> >>>> On 16 Aug, Dirk Heinrichs wrote: >>>> >>>> >>>>> Am Sonntag 16 August 2009 21:12:30 schrieb Dirk Heinrichs: >>>>> >>>>> >>>>> >>>>>> 2) No need to unmerge anything (except one or two blockers). >>>>>> >>>>>> >>>>> However, you can unmerge 4.2.x, if you like to. >>>>> >>>>> >>>>> >>>> How to do that in a simple way? >>>> >>>> Unfortunately, >>>> emerge --unmerge kde-base/kde-meta:4.2 >>>> only unmerges the meta package itself. >>>> >>>> Thanks for a hint ( I'm afraid of any kde updates >>>> since they always have created more headaches than any >>>> other package or set of packages ) >>>> >>>> >>>> >>> Not tested but should work. Use the -p option to make sure. >>> >>> Unmerge kde-meta:4.2 >>> emerge --depclean -p >>> >>> If that looks good, remove the -p. It should only remove kde:4.2 and >>> what depends on it. If you wait a while, I may be about to do this. >>> I'm doing the same thing as you. This DSL is soooooo cool. :-) >>> >>> >> >> I have difficulties doing so. 'emerge --depclean' requires a recent >> emerge --update --newuse --deep @system @world >> which tries to update kde, as well. >> I'm just trying to mask all kde-base packages, then doing emerge >> --update --newuse --deep @system @world >> >> Still, quite tedious. >> Helmut. >> >> > > It may not work but then again it might. emerge --depclean -p > kde-meta:4.2 .
This gives >>> No packages selected for removal by depclean Helmut.
