Summary: | sys-apps/portage: FEATURES=keepwork: Space required, why? | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Toni Ballesta <info> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toni Ballesta
2015-10-17 09:05:47 UTC
Sorry for the faulty text, I should check first... Another solution is if emerge detect the same instance on temporary dir, it can rest the directory space used actually to the limit required by the ebuild. FEATURES=keepwork is more of a debugging tool than anything else. It's not intended for general use. You probably want FEATURES=ccache instead. From the make.conf man page: keepwork Do not delete the ${WORKDIR} directory after the merge process. ${WORKDIR} can then be reused since this feature disables most of the clean phase that runs prior to each build. Due to lack of proper cleanup, this feature can interfere with normal emerge operation and therefore it should not be left enabled for more than a short period of time. Yes I know, but not delete the temporary files before or after, and you can continue the build operation. Ccache probably is a good engine, but the man page warns the first build is slower and I need build only one time. Nevertheless The base of the bug is on keepwork, not on ccache. I think removing or resting space required on detected instance is a good feature/solution for limited spaces. Regards. |