Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 887755 - sys-apps/portage: include app-alternatives/* USE flags in emerge --info
Summary: sys-apps/portage: include app-alternatives/* USE flags in emerge --info
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-21 18:48 UTC by Michał Górny
Modified: 2023-12-24 17:26 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2022-12-21 18:48:44 UTC
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.
Comment 1 Ulrich Müller gentoo-dev 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 archtester Gentoo Infrastructure gentoo-dev Security 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ć gentoo-dev 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.