Summary: | When resuming a build that failed late in the process, portage repeats install step | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andrew Cowie <andrew> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | minor | CC: | antarus |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrew Cowie
2004-02-09 00:23:31 UTC
just to be sure we use the same terminology: do you mean the install or merge phase ? I mean install. Stuff that happens in the src_install() step is being repeated, whereas it is noting that the src_compile step has already been completed and can be skipped. I only notice this if something happens *after* install is complete, which, admittedly, is rare. Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;) > Putting a hold on feature requests for portage as they are drowning out the
> bugs.
This is not a feature request. I've documented inconsistent behaviour. That is a
bug. Low priority, certainly, but a bug all the same.
It's not resolved, and so I'm re-openning it.
AfC
Strangely, it's not inconsistant behaviour. Portage should run cleaning on the directory prior to trying to build it, I'd bet you have keepwork on and it's getting reused. In terms of ebuild.sh actual execution, setup/unpack/compile aren't repeated, install is. it's odd, but it's legacy behaviour (something changed in developmental branch). Reopen if you don't have said features on please... |