| Summary: | sys-apps/portage: please provide ability to call 'ebuild ... unpack' with unsatisfied REQUIRED_USE | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
| Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Yeah, a warning message should be sufficient. Although, we should probably block commands like 'package' and 'merge', to prevent installation with invalid USE state. How would this work if there's conditional distfiles in SRC_URI? I guess we can let people shoot themselves in the foot, it's not a big deal here. |
$ ebuild bumblebee-3.0-r1.ebuild --force unpack The following REQUIRED_USE flag constraints are unsatisfied: || ( video_cards_nouveau video_cards_nvidia ) It would be great if it could just unpack the file with --force. It's unlikely that unsatisfied REQUIRED_USE would actually cause problems with that, esp. considering that 'ebuild' doesn't even check dependencies...