Jack Byer wrote:
It would be nice if there were some way to mark particular packages that should never be compiled in parallel (like the trick for using a using a separate, non-tmpfs build directory for large packages). The "load-explosion" you describe is bad enough with regular packages but when firefox, xulrunner, chromium and libreoffice all decide to start compiling at the same time it turns into a complete nightmare.
I think it has that already. I have noticed several times that mine will only be working on one package and have a lot of packages left to update. When that single package is done, it loads up several and does them at the same time. Something tells emerge not to run them at the same time and I assume it is in the ebuild somewhere.
I have to have tmpfs in use when LOo comes up for a compile. I have more memory than I have space on /var. If I don't have portages work directory on tmpfs, the compile fills up /var and dies. Ironic that what works for one fails for another.
Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
