When executing 'ebuild blah.ebuild badcommand' the error reported should list the valid commands that are available. Reproducible: Always Steps to Reproduce: 1. Run 'ebuild /usr/portage/sys-apps/dcron/dcron-2.9.ebuild upack' Actual Results: !!! doebuild: Please specify a valid command. Expected Results: A more verbose error including the invalid command entered and the currently available commands. This might be a personal issue, but it seems that error messages should provide fairly specific reasons for the errors that have occurred.
Created attachment 30104 [details, diff] Adds more verbose error reporting to doebuild. This patch applies against /usr/lib/portage/pym/portage.py from sys-apps/portage-2.0.50-r6. The new error message with this patch is: ebuild ez-ipupdate-3.0.11_beta8-r1.ebuild upack !!! doebuild: 'upack' is not one of the following valid commands: !!! clean compile config depend digest fetch !!! help install manifest merge package postinst !!! postrm preinst prerm qmerge rpm setup !!! touch unmerge unpack
Bug has been fixed and released in stable portages on or before 2.0.51-r2
