Following Bug 382721 I reported against nvidia-cuda-toolkit, I think it would be an enhancement of portage if emerge packagename and emerge --depclean were coherent when resolving dependencies. exempli gratia : - gcc-4.4.5 emerged with the multislot use flag. - emerge packagename apparently considers that it fits for satisfying a build specifying a sys-devel/gcc:4.4 runtime dependency. - But emerge --depclean apparently does not consider things identically and fails processing because : ----------------------------------------------- * Dependencies could not be completely resolved due to * the following required packages not being installed: * * sys-devel/gcc:4.4 pulled in by: * dev-util/nvidia-cuda-toolkit-4.0 ---------------------------------------- It would of course be simpler (on the user point of view) if both were considering that gcc-4.4.5 slot satisfies the dependency on a gcc-4.4 slot but if emerge --depclean must / can not be modified that way then emerge packagename should behave identically and should not consider that the dependency is satisfied too. Reproducible: Always
*** Bug 382721 has been marked as a duplicate of this bug. ***
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=70e7107bfb01225c0aac74ce32f66b1c3b0d4d2d
This is fixed in 2.1.10.18 and 2.2.0_alpha58.