Bug 703064

Summary:	sys-apps/portage-2.3.81 allow to show as much possible of USE conflicts for each run
Product:	Portage Development	Reporter:	Pacho Ramos <pacho>
Component:	Core - Dependencies	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	normal	CC:	kingjon3377
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Pacho Ramos gentoo-dev

2019-12-16 08:06:29 UTC

For example from this message:
 * Error: circular dependencies:

(dev-python/importlib_metadata-0.23-r1:0/0::gentoo, ebuild scheduled for merge) depends on
 (dev-python/zipp-0.6.0-r1:0/0::gentoo, ebuild scheduled for merge) (buildtime)
  (dev-python/pytest-4.6.7:0/0::gentoo, ebuild scheduled for merge) (buildtime)
   (dev-python/importlib_metadata-0.23-r1:0/0::gentoo, ebuild scheduled for merge) (runtime)

It might be possible to break this cycle
by applying any of the following changes:
- dev-python/importlib_metadata-0.23-r1 (Change USE: -test)
- dev-python/zipp-0.6.0-r1 (Change USE: -test)

Note that this change can be reverted, once the package has been installed.

Note that the dependency graph contains a lot of cycles.
Several changes might be required to resolve all cycles.
Temporarily changing some use flag for all packages might be the better option.

--------------------

This phrases:
Note that the dependency graph contains a lot of cycles.
Several changes might be required to resolve all cycles.
Temporarily changing some use flag for all packages might be the better option.

Look to suggest that portage could maybe output the information of that "lot of cycles" too for trying to list more packages to get built without USE test and, then, don't need to re-run emerge @world so many times (for not needing to rebuild the system without USE test for later try to re-enable it)

Thanks