On Monday, 18 September 2023 17:13:04 BST Alan McKinnon wrote: > I did read all those but no matter how you move things around you still > have only X resources available all the time. > Whether you just let emerge do it's thing or try get it to do big packages > on their own, everything is still going to use the same number of cpu > cycles overall and you will save nothing.
That isn't the point. The point is that it takes twice as long, and it wastes the machine's resources while I twiddle my thumbs waiting for it. > If webkit-gtk is the only big package, have you considered: > > emerge -1v webkit-gtk && emerge -avuND @world? Of course. > What you have is not a portage problem. It is a orthodox parallelism > problem, and I think you are thinking your constraint is unique in the work > - it isn't. No, I think my problem has not been tackled by the portage developers. > With parallelism, trying to fiddle single nodes to improve things overall > never really works out. See above. -- Regards, Peter.
