On Mittwoch, 2. Januar 2008, BRM wrote: > I installed KDE yesterday via "emerge kde -vuD", and just remembered > today about "kde-meta", which installs a lot more. In running "emerge > kde-meta -vuD", I get 250 new packages, and 245 blocks, with 1 upgrade. > What is the _best_ path forward? Should I just stick with my current > build of kde? Or is there an easy way to remove all the blocks and then > push in kde-meta? Is it worth it? > > TIA, > > Ben
kde and kde-meta install the same apps. One is in monolith packages, the other one uses the split ebuilds. If you install everything, monolith is a lot faster. But some important useflags are only used and the features enabled with split ebuilds (grrrr). Like kdenetwork&kopete. With kdenetwork kopete emerges without the history plugin, even if all useflags are set (which sucks greatly). With split ebuilds, kopete gets its history plugin (there is no logic behind this - but the devs decided it this way...). You don't have to unmerge kde first. You can do it in a more 'gradual' way. For example: first unmerge kdenetwork, then emerge kdenetwork-meta. Unmerge kdebase, emerge kdebase-meta and so on. -- [EMAIL PROTECTED] mailing list
