|Summary:||sys-apps/portage: include app-alternatives/* USE flags in emerge --info|
|Product:||Portage Development||Reporter:||Michał Górny <mgorny>|
|Component:||Enhancement/Feature Requests||Assignee:||Portage team <dev-portage>|
|Severity:||normal||CC:||arsen, sam, ulm|
|Package list:||Runtime testing required:||---|
Description Michał Górny 2022-12-21 18:48:44 UTC
Comment 1 Ulrich Müller 2022-12-22 10:37:43 UTC
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.
Comment 2 Sam James 2022-12-22 10:57:20 UTC
It needs to contain enough information to be useful in determining likely causes of a bug.
Comment 3 Arsen Arsenović 2023-01-30 14:22:58 UTC
(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.