Summary: | ebuild and emerge tools behave differently when the last command in an eclass returns != 0 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED NEEDINFO | ||
Severity: | critical | CC: | gengor, howard_b_golden, pacho |
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Petteri Räty (RETIRED)
2008-10-01 15:51:57 UTC
I don't observe any inconsistency when I try a local test case. It dies just like I'd expect it to. Are you able to reproduce the problem? Please reopen if you can reproduce and provide more info. (In reply to comment #2) > Please reopen if you can reproduce and provide more info. > the ebuild tool seems to die properly now |