| Summary: | Have more precisions about the effect of use flags on a specific package | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Guillaume Bouchard <guillaume> |
| Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | CC: | antarus |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
I am currently working on a script that does this, you do emerge -pv | script and it will pull descs from use.desc and use.local.desc. however, it's not done or near enough for testing. Please stay tuned however ;) |
When i emerge -pv a package, i have the list of the uses flags that affect the package. In some case i can understand the effect, exemple gst-plugins with alsa, esd and oss flags, i'm sure that i don't need oss and esd (it's just an exemple ;o). But in some cases, i don't know the effect of each flags. Exemple, the gtk flags in gcc ? What is it effect ? Can i remove it even if i use gtk ? This can broke my gtk build ? Or this flags is just here for build a gcc gui in gtk ? So it's why i propose that every owners of a package explain (in the ebuild per haps) what is the effect of a flag on the package. So, with this option, i can remove and add flags for each packages more easier without look in the ebuild, or in the package archive. Exemple of use (with very stupid explaination of use) # explain_flag rp-pppoe USES flags for rp-pppoe was : - X : Build some gui frontend for rp-pppoe - tcltk : The gui frontend will be build with TK and not motif by default - xmms : Build a deamon for rp-pppoe who allow xmms remote to display the network status instead of the sound volume (stupid use, for exemple) I hope this is understandable (my writing skill so bad...) Reproducible: Always Steps to Reproduce: