Currently it could be really hard to figure out what emerge did in the end, especially if --keep-going is used and re-evaluations occur, or when FEATURES=test-fail-continue is used and tests fail. Portage spits some elog messages at the end but that's far from readable. What I'd like to see is emerge outputting a full summary of operation at the end -- i.e. after any re-evaluations necessary. I'm thinking of a *complete* package list, clearly stating: - whether package was built, tested, installed successfully, - optionally indicate whether any elog was spitted, - which packages were skipped due to --keep-going. Something looking like: # full success with no tests and binpkg built dev-foo/bar-1.2.3 build:[yes] test:[n/a] bpkg:[yes] inst:[yes] # src_configure failure dev-foo/baz-1.2.3 build:[no - configure failed] # --keep-going skipped dev-foo/frob-1.2.3 skipped due to unsatisfied deps # src_test failure without FEATURES=test-fail-continue dev-bar/foo-1.2.3 build:[no - test failed] test:[no] # src_test failure with FEATURES=test-fail-continue dev-bar/foo2-1.2.3 build:[yes] test:[no] bpkg:[yes] inst:[yes] # file collision dev-bar/frzx-1.2.3 build:[yes] test:[no] bpkg:[yes] inst:[no - file collision] # preinst failure dev-bar/frzp-1.2.3 build:[yes] test:[no] bpkg:[yes] inst:[no - preinst failed] # install from binpkg dev-bin/zzz-1.2.3 build:[n/a] test:[n/a] bpkg:[n/a] inst:[yes]
