Summary: | Improved output for 'emerge --buildpkgonly' dependency failure | ||
---|---|---|---|
Product: | Portage Development | Reporter: | David <write2David> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | roman.zilka |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David
2011-12-15 05:07:16 UTC
Alternatively, we might change the meaning of --buildpkgonly so that it merges the dependencies and just doesn't merge the package(s) given as arguments when possible. (In reply to comment #1) > Alternatively, we might change the meaning of --buildpkgonly so that it > merges the dependencies and just doesn't merge the package(s) given as > arguments when possible. +1 user vote for that. I.e., "merge as many pkgs as possible and meaningful". |