I think it would be helpful to include the USE flags selected on app-alternatives/* in `emerge --info`. This could e.g. help when you suspect that a weird configure failure is related to CONFIG_SHELL. I can think of two options: 1. Just add a cheap hack into Portage to list USE flags on all packages in app-alternatives/*. 2. Extend info_pkgs output to include USE flags, and add interesting app-alternatives/* packages there.
I am undecided whether these should be included. emerge --info output is already too long for my taste. If we're going to include them, then the second option looks more future-proof to me.
It needs to contain enough information to be useful in determining likely causes of a bug.
(In reply to Ulrich Müller from comment #1) > I am undecided whether these should be included. emerge --info output is > already too long for my taste. > > If we're going to include them, then the second option looks more > future-proof to me. In case ``emerge --info'' isn't meant to serve as a tool to quickly gather bug report information, an ``emerge --bugreport'' which contains this info and more seems appropriate, though I'm not sure that's the case.