| 1 |
On Wednesday, November 22, 2017 3:34:56 PM CET Wols Lists wrote: |
| 2 |
> On 22/11/17 14:11, Tsukasa Mcp_Reznor wrote: |
| 3 |
> > You won't get build failures or dependency problems, portage is built to |
| 4 |
> > handle emerging multiple packages that do not depend on each other |
| 5 |
> > simultaneously. |
| 6 |
> > it will not ever build a dependency and the main program at the same time. |
| 7 |
> |
| 8 |
> Are you sure? |
| 9 |
> |
| 10 |
> You *shouldn't* get problems, but I'm sure I have hit that problem, and |
| 11 |
> I think it's down to buggy ebuilds. |
| 12 |
|
| 13 |
buggy, as in, at least one dependency missed. |
| 14 |
|
| 15 |
> Starting the emerge again fixes it, because cocked-up dependencies will |
| 16 |
> sort themselves out first time round, and the second time the problem |
| 17 |
> has gone away. |
| 18 |
|
| 19 |
2nd time the dependency might have been installed already. |
| 20 |
Sometime it hasn't. |
| 21 |
|
| 22 |
This can also cause a failure when not using parallel builds for exactly the |
| 23 |
same reason. |
| 24 |
|
| 25 |
-- |
| 26 |
Joost |
Archives