| 1 |
On Fri, 27 Oct 2017 14:58:13 +0100 Peter Humphrey wrote: |
| 2 |
> On Fri, 27 Oct 2017 12:52:54 -0000 |
| 3 |
> Helmut Jarausch <jarausch@××××××.be> wrote: |
| 4 |
> |
| 5 |
> > I have a problem with emerge for a long time. |
| 6 |
> > Sometimes I need to (re-)emerge many packages like in an |
| 7 |
> > emerge --emptytree @world |
| 8 |
> > |
| 9 |
> > Because I use several overlays, there are problems with a lot of |
| 10 |
> > packages. |
| 11 |
> > Unfortunately, emerge shows me just the first problem (like a missing |
| 12 |
> > USE-flags) and then terminates. |
| 13 |
> > Is there any means to let emerge go and report several (all) problems |
| 14 |
> > which are independent of each other? |
| 15 |
> |
| 16 |
> EMERGE_DEFAULT_OPTS="--keep-going" ? |
| 17 |
|
| 18 |
No, --keep-going allows to continue as long as possible after a |
| 19 |
build failure. Helmut asks about dependecies resolution failures, |
| 20 |
e.g. in some package REQUIRED_USE is not met, or circular |
| 21 |
dependency occurs and so on. |
| 22 |
|
| 23 |
AFAIK there is no way to use keep-going like option for deps |
| 24 |
resolution, because first error may trigger a lot of others and |
| 25 |
there will be inevitably false errors, because the dependency tree |
| 26 |
was not fully built. |
| 27 |
|
| 28 |
Best regards, |
| 29 |
Andrew Savchenko |
Archives