Summary: | Seperate portage error (and die msg) from build errors with indicator (colorize) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Arvid Picciani <aep> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED LATER | ||
Severity: | normal | CC: | jakub, marten |
Priority: | High | Keywords: | NeedPatch |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Arvid Picciani
2006-07-11 06:53:09 UTC
I'd like: ^^^^^ when asking for help, include the error(s) above this line ^^^^^ I think people who don't get the current message would ignore any more "user-friendly" message as well, I mean we can't be much more explicit than "don't post this message". Can't really do much if people don't read the stuff. The problem might be that there are exclamation marks in front of these lines, so people think: "That's got to be the most important part of the log." Perhapps one could color the phrase "post the topmost build error" in red. Still I think the suggested line before the portage error handler would be helpful to people who don't have a clue what a "build error" might be, so they at least start looking for it at the right place. Can we WONTFIX this? People who can't be bothered to read won't read no matter what, the message is damn explicit as for what to post, as already said in comment #2. There will always be some beginner that pastes the wrong thing somewhere. If we had some official Gentoo documentation about interpreting build errors, then we might print a link to it when not in --quiet mode. We already do something similar when emerge exits due to blockers, since beginners are known to ask questions about that extremely frequently. If someone can write up a nice howto for this I'll add it to our project page and add a link in the message. |