[gentoo-dev] Re: Is || ( Atom... ) broken?

[Duncan <1i5t5.duncan@cox.net>]

Greg Turner posted on Mon, 07 Jul 2014 16:42:08 -0700 as excerpted:

> *Indeed, I'd estimate I often have to wait a half-hour on my 32GB
> workstation to get a plan from emerge -DuavN @world, so for me that's a
> bigger problem than anything else about portage right now.

Wow.  I didn't realize and to some extent had forgotten how bad things 
had gotten, as I (1) run an SSD-based tree now, and (2) set backtrack=0 
so portage does its best only one time thru and spits out the result, 
allowing me to at least see what it's doing in reasonable time, such that 
I can resolve the thing manually if I need to.

I haven't had to resort to --nodeps yet, but I do often emerge subsets of 
the whole, reducing the number of updates until I have a much smaller 
update set to work with, then sometimes run --tree and/or even go look at 
individual ebuild deps, to see why something's getting pulled in.  And I 
guess running no-multilib means I bypass at least some of the issues, 
too.  That and a USE=-* base probably help a lot, but I've no idea 
whether the fully negated @system so there's no system set to deal with 
helps or hurts.

But from the sound of things, default backtrack=10, multilib, full 
@system set and default profile use, on spinning rust, is getting all but 
intolerable now. =:^(

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman