| Summary: | sys-apps/portage: Confusing UX (output message) if portage says "the build log is here" when fail-clean is enabled, but the build log is missing. | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | sozuba <sozuba> |
| Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Tail end of the emerge ouput when package build fails.
emerge --info output for package eww. |
||
Created attachment 873418 [details]
emerge --info output for package eww.
|
Created attachment 873417 [details] Tail end of the emerge ouput when package build fails. When a package build fails, the output message says "The complete build log is located at '/var/tmp/portage/....../build.log'". But the build log is deleted when 'FEATURES=fail-clean' is enabled in make.conf'. This is confusing especially for newbies like myself, when the real and full impact of 'fail-clean' isn't understood. Solution: It would be better, if emerge would show/add "(deleted because of FEATURES="fail-clean")" to add more context. The output/log attachment here is an example for such a case for package 'gui-apps/eww-0.4.0-r1'.