When a dependency calculation fails, it's common for emerge to output a bunch of slot conflicts involving built slot operator deps, even though those conflicts may be solvable after other issues have been resolved. This noise makes it difficult for users to recognize the issues really require attention.
If emerge would filter out noise from conflicts involving built slot operator deps, then it would help users to focus on the issues that really require their attention. For example, this might be implemented by automatically retrying a calculation as though --ignore-built-slot-operator-deps=y had been enabled.
(In reply to Zac Medico from comment #0)
> For example, this might be implemented by automatically retrying a calculation
> as though --ignore-built-slot-operator-deps=y had been enabled.
Or maybe it should even try that first, so that it can fail earlier it that calculation detects a problem.
You're entering a slippery ground here. Remember that slot rebuilds can trigger actions that otherwise wouldn't be triggered -- e.g. downgrades due to missing/masked installed packages or rebuilds of packages outside @world. This can have major effects on resulting dependency tree.
This could be similar to:
And maybe changing the order of the output would still help, I mean, pushing the conflicts that are not related with the build slot issues to the end of the output to ensure the user handles that errors first
As first step, we could integrate some of the FAQ information into the emerge man page description of --ignore-built-slot-operator-deps=y. We might even make emerge suggest to use --ignore-built-slot-operator-deps=y when it detects conflicts involving built slot operator deps.
*** Bug 674886 has been marked as a duplicate of this bug. ***