Summary: | Why I prefer monolithic KDE | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kevin O'Gorman <kogorman> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED REMIND | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kevin O'Gorman
2006-06-11 16:12:16 UTC
*** Bug 136602 has been marked as a duplicate of this bug. *** (In reply to comment #1) > *** Bug 136602 has been marked as a duplicate of this bug. *** > I know this is a late response.. in a situation like that I would emerge -C all the blocking packages, and then emerge kde-meta or whatever, and hope there's no compilation failure. I also agree that portage doesn't protect anything from being in an illegal state, as far as I know, and the only solution to that is to emerge -vua(N)D world until there's nothing to do. I hope you managed to get help from somewhere other than this bug though. Ehm..... when you plan to update your kde to a newer version, you just unmerge all the monolithic ebuilds and then pull-in all the meta (or just kdebase-meta and the splitted ebuilds for your other needs). Using the meta grants you a 1:1 conversion from your previos versions.... P.S.: for things missing that don't need to compile, try ebuilds with extra in the name or check http://docs.kde.org/ Thanks for feedback, closing this as it's not really a bug. |