On Mon, Jul 9, 2012 at 10:56 AM, Rich Freeman <ri...@gentoo.org> wrote: > On Mon, Jul 9, 2012 at 10:11 AM, Peter Stuge <pe...@stuge.se> wrote: >> Rich Freeman wrote: >>> It also seems like the current portage output is giving the user some >>> contradictory and counterproductive advice. It seems like there are >>> really only two possible choices >>> 1. The user could choose to not install chromium. >>> 2. The user could enable icu for qt-webkit. >> >> Do you get the same suggestions from portage if you attempt emerge >> kde and chromium one at a time? > > I'll test it out on a fresh install, but that will take a number of > hours (a total of 694 packages between them, which will take a while > even on 4 cores, and warm up the office as well...). If I try to > start out with chromium first the initial suggestion is to enable icu > on libxml2, and if I try to start out with kde-meta the initial > suggestion is to enable minizip on zlib (unrelated to this whole > issue). > > I don't have a copy of the message but when I got the update to > qt-webkit the message was fairly cryptic when it added the !icu? > dependency on libxml2. If anything I think it was less clear. > > Let me give that upgrade a try both ways, but it might take a few days > to have all the results of that.
When tracking down why glibc updates were killing my systems, I wrote an install script to accelerate the install-update-fail-retry cycle. You may find it useful: https://github.com/mikemol/gentoo-install It shouldn't require *too* much modification to automate what you're trying to test. I intend to modify it to work in chroot environments, as a prelude to some build-related bug reports I'm sitting on. -- :wq
