I was recently performing several emerges at the same time while away, and one (emerge -e system after a libstdc++ upgrade) failed, followed by another emerge (emerge -u koffice-meta) failing. I couldn't resume the system emerge because the koffice-meta emerge had failed more recently, so I had to start over. I propose that a "history" of, say, the last 5 failed emerges, end they may be listed by passing the --resume-list argument to emerge, and may be specified by passing --resume-? where ? is a whole number between 1 and 5, larger numbers indicating emerges further back in the history. This would permit as many as five concurrent emerges to fail without the risk of having to restart the emerge. I will endeavor to create a patch to provide this and will post it upon completion.
*** This bug has been marked as a duplicate of 150104 ***
The eselect module proposed in bug 150104 won't solve this.
Parallel emerge activities, though the may work in many cases, are completely unsupported at this time. It is planned though. See bug 147516.
*** Bug 150228 has been marked as a duplicate of this bug. ***
