Sorry if this is the wrong place to post this. I got tired of having to go back and edit my command line after typing a package short name that was ambigious so I change the emerge script to list the possiblities and let me choose which one to use. It does this only when the --ask flag is specified so as not to mess up any non-interactive script that may call emerge. Here's the general idea: *************** localhost temp # emerge mldonkey --ask These are the packages that I would merge, in order: Calculating dependencies !!! The short ebuild name "mldonkey" is ambiguous. Please specify !!! one of the following fully-qualified ebuild names instead: [1] app-emacs/mldonkey [2] net-p2p/mldonkey ...done! [ebuild N ] app-editors/emacs-21.3-r4 [ebuild N ] app-emacs/mldonkey-0.0.3c *************** I've added both a diff to the emerge script in portage-2.0.50-r10 and a copy of the patched emerge script. Please consider adding this to the software. Thanks, Todd Kirby <doubleshot@pacbell.net> Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 38269 [details, diff] patch to emerge to interactively resolve short name ambiguities
Created attachment 38270 [details] emerge with ambigchoice.diff patch applied
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Reopening for duping
*** This bug has been marked as a duplicate of bug 135063 ***
