Re: [gentoo-user] Portage: Complaining about multiple incidents at once

["Mickaël Bucas" <mbucas@gmail.com>]

Le dim. 19 avr. 2020 à 13:03, Gerion Entrup <gerion.entrup@flump.de> a écrit :
>
> Hi,
>
> does Portage have a "don't stop" mode?
>
> With that I mean the following:
> I'm doing updates with
> emerge -auND world --keep-going --quiet-build --verbose-conflicts
>
> Portage then often stops, saying a dependency keyword is missing or a
> useflag etc. However, this always happens incident after incident, so I
> need to run portage multiple times.
>
> Is there a way to instruct portage to just say: "Ok, here is a
> configuration fix necessary, maybe a use flag must be added, but let's
> assume, the user does this and the use flag is set now. What do I need
> to do next."
>
> Without checking it, this behaviour seems to be more the case in prior
> portage version (complaining about multiple incidents at once).
>
> Best,
> Gerion

Hi Gerion

I believe that what you are looking for are the options starting with
--autounmask, which affect the initial analysis of the build tree,
which is the source of the complaints about missing keywords or USE
flags.
The --keep-going option does a great job at continuing to build other
packages when one build fails.

There are a bunch of them so I don't know how much you'd like to use
but it seems tailored to go forward in almost any situation !
They are well described in "man emerge"
--autounmask [ y | n ]
--autounmask-backtrack < y | n >
--autounmask-continue [ y | n ]
--autounmask-only [ y | n ]
--autounmask-unrestricted-atoms [ y | n ]
--autounmask-keep-keywords [ y | n ]
--autounmask-keep-masks [ y | n ]
--autounmask-license < y | n >
--autounmask-use < y | n >
--autounmask-write [ y | n ]

Adding --backtrack=COUNT with COUNT > 10 (the default value) may push
Portage to look forward a bit more.

However, as I don't use them, I don't know what stability you could
expect from your system after activating any or all of them.

Best regards
Mickaël Bucas