The number of package increase & the possibility of package with the same short name is increasing ... ( like listen beagle ... ) Exemple : emerge -pv listen !!! The short ebuild name "listen" is ambiguous. Please specify !!! one of the following fully-qualified ebuild names instead: media-sound/listen dev-tinyos/listen It's will be great if the portage will look on our world file & check if only one of them is already installed & select this-one. Exemple : I have already installated media-sound/listen , a emerge -pv listen will automatically select the media-sound/listen ...
this is rather unfriendly for any utility trying to do a general lookup... and adding an option to disable trying to alias the name isn't much of an option ;)
Only a mind-reader would know for certain which one to choose. This is why all packages in ebuilds are prefixed with their group. Invalid, I'd say.
*** Bug 156789 has been marked as a duplicate of this bug. ***
For me, a automatic select ( with a time before selection, like the emerge --prune ) is great. But if you think it's will be confusing, i closing this request. You are the chief ...
(In reply to comment #4) > For me, a automatic select ( with a time before selection, like the emerge > --prune ) is great. > But if you think it's will be confusing, i closing this request. > > You are the chief ... > To explain a bit (cause i like to ramble and spam people with bugmail), currently the lookup call is implemented in portage.py. Other tools besides emerge use this call to do package lookups (as Brian stated). A workaround would be to return a list of packages; thus "emerge beagle" would really be like emerge <any category>/beagle since you didn't specify. I don't think users want this behavior, and it's not what you requested, so then we have to write more code in emerge to look at the list of returned packages and try to guess at what you really wanted. And guessing sucks, because we might be wrong some random percent of the time and then someone will file a bug because emerge beagle emerged the wrong package :x Really the case I just described above is why this is a bad idea, IMHO :)
