Alan McKinnon <alan.mckinnon <at> gmail.com> writes: Volker and Alan,
> Finally, try to use sets if possible. The split -meta ebuilds were an ugly > hack until sets made it into portage. They were orders of magnitude better > than monolithic, but sets are just so much cleaner than -meta. Plus you get > to easily define what's in a set if the standard ones don't suit your needs. OK, I got it, use SETS instead of kde-meta. Where do I read up on using SETS? I see "set" in the emerge manpage, but it seem, brief. How do you use the default "sets" when upgrading to kde-4.2.x? Any examples or further reading? > I'm finding issues with exiv2, libkeviv2 and stuff that uses it. Like > gwenview, okular and krita. But that's the kind of thing that happens > occasionally in ~arch Well this is just one test laptop. The approach is to now put kde-4.2.0 on this laptop, use it until some comfort is found with kde-4.2.x and then slowly upgrade the rest of the machine I'm admin over. Point well taken about skipping the removal of kde-meta-3.5.9. Just leave it on the laptop? I thought I had read that that causes problems. This laptop is my test box, so loosing kde-meta-3.5.9 is no big deal, as I have another workstation.
