| Summary: | Portage should have a feature to write .info files with --info | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Diego Elio Pettenò (RETIRED)
2009-12-01 20:21:34 UTC
The option could be a tri-state of "never", "on-failure", and "always", if you want to support testers who need to report that a particular combination works for them, and let the default be "on-failure" since typical users will not report successful builds. If the file is written under $T on failure, then it would automatically be cleaned up if the user deletes the whole working area, which is standard practice for a failed build that either has been reported, or will not be reported. Users who set it to "always" could have it written somewhere else, or perhaps even just included directly in the existing build log. Putting it inline is a bit unclean, but build logs are presently free form, so no tools should be seriously broken if this is added. I definitely like Kevin's idea of having it a three-state and using ${T} for on-failure. Inlining it might be a bit too much maybe, but that would also work for me (even better one less file to attach on my bugs :P — on the other hand, bigger files, which might get rejected :()
|