On Mon, Jul 9, 2012 at 10:56 AM, Rich Freeman <[email protected]> wrote:
> I'll test it out on a fresh install, but that will take a number of
> hours
If I install chromium first, I get the following messages when I try
to install kde-meta:
The following USE changes are necessary to proceed:
#required by dev-db/virtuoso-server-6.1.4-r1, required by
dev-libs/soprano-2.7.6[virtuoso], required by
app-office/akonadi-server-1.7.2,
required by kde-base/kdepim-runtime-4.8.3-r2, required by
kde-base/kdepim-meta-4.8.3, required by
kde-base/kde-meta-4.8.3[semantic-desktop], required by kde-meta (argument)
=sys-libs/zlib-1.2.5.1-r2 minizip
#required by x11-libs/qt-webkit-4.8.2[gstreamer], required by
kde-base/kdebase-menu-icons-4.8.3, required by
kde-base/kdebase-runtime-meta-4.8.3, required by
kde-base/kdebase-startkde-4.8.3, required by kde-base/kdebase-meta-4.8.3,
required by kde-base/kde-meta-4.8.3, required by kde-meta (argument)
=dev-libs/libxml2-2.8.0_rc1 -icu
You'll note that in this case there is nothing to suggest simply
enabling icu for qt-webkit.
If I emerge kde-meta first then I get the following when I try to
emerge chromium:
The following USE changes are necessary to proceed:
#required by www-client/chromium-20.0.1132.43, required by
chromium (argument)
=dev-libs/libxml2-2.8.0_rc1 icu
Then if I set the icu use flag on libxml2 it works. Apparently it
doesn't realize that I'm about to break qt-webkit. Portage doesn't
check use dependencies on existing packages when you go to rebuild
something?
I hope that helps...
Rich
