This is after "emerge -C virtual/mpg123 media-sound/mpg123" -- cut -- ssuominen@unique ~/gentoo-x86/profiles $ sudo emerge -av mpg123 These are the packages that would be merged, in order: Calculating dependencies - [ Results for search key : mpg123 ] [ Applications found : 2 ] * media-sound/mpg123 Latest version available: 1.7.3 Latest version installed: [ Not Installed ] Size of files: 1,125 kB Homepage: http://www.mpg123.org Description: a realtime MPEG 1.0/2.0/2.5 audio player for layers 1, 2 and 3. License: GPL-2 LGPL-2.1 * virtual/mpg123 Latest version available: 0 Latest version installed: [ Not Installed ] Size of files: 0 kB Homepage: http://www.gentoo.org Description: Virtual for command-line players mpg123 and mpg321 License: !!! The short ebuild name "mpg123" is ambiguous. Please specify !!! one of the above fully-qualified ebuild names instead. ... done! -- cut -- Same problem for virtual/cdrtools. Can we please get the real package name preferred in the dep calculation first? It's pretty annoying for users "emerge -av cdrtools" or "emerge -av mpg123" when it isn't coming from a virtual pulled in by 3rd party ebuild.
This is sys-apps/portage-2.1.6.13 by the way, the problem has been there for quite a while, Sorry I haven't opened a report before.
And just to be clear, I'm proposing this for the virtual handling only, leaving alone the pkgs that just happen to have same name in tree..
Created attachment 194091 [details, diff] If we have to decide between a non-virtual and one or more virtual packages, choose the non-virtual package without calling ambiguous_package_name.
Update: virtual/mpg123 isn't in tree anymore, it's only virtual/cdrtools now that *I know of*. If you don't like the idea, feel free to close this off... it's just a suggestion
(In reply to comment #3) > Created an attachment (id=194091) [details] > If we have to decide between a non-virtual and one or more virtual packages, > choose the non-virtual package without calling ambiguous_package_name. > Thanks, this is in svn r14522.
This is fixed in 2.1.7 and 2.2_rc45.