If I add a package under /etc/portage/profile/package.provided and attempt to emerge only its deps, Portage will refuse to install anything. Since Portage does such a good job at atomizing packages, I think it makes no sense to block the installation of an entire dependency stack just because the administrator specifies *one specific* package as otherwise provided. If the dependencies were also provided, they would also be mentioned. Even worse, this feature (making Portage ignore one package specifically from the dependency graph) is otherwise unattainable short of creating a duplicate dummy ebuild which installs nothing (with the corresponding updating issues that brings), or adding a USE flag to the ebuild, basically replicating the package.provided functionality, but without the quirk of also ignoring dependnecies. It would be really nice to not let package.provided impact dependency resolution. Reproducible: Always
