Summary: | catalyst does not remove stage directories after successful builds | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Markos Chandras (RETIRED) <hwoarang> |
Component: | Catalyst | Assignee: | Gentoo Catalyst Developers <catalyst> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bkohler, catalyst, zerochaos |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 608058 | ||
Bug Blocks: |
Description
Markos Chandras (RETIRED)
2013-08-15 13:08:48 UTC
Just for an FYI, all these .autoresume files and build directories are not removed in current catalyst master's code either. But it is something that needs to be addressed. For the build directories, I think it would be best to put in a spec option to remove them after successful completion. That way it is a users choice as to whether they are removed or not. perhaps cleanup by default and have options="keepwork" like portage? Also seedcache specifically requires the stage to not be cleaned up. I personally find seedcache slows down my builds significanly, maybe that's just me. I've made the needed changes to the 3.0 branch in catalyst.git. Emerge catalyst 2.9999 to get them for testing. To use it properly: Add keepwork to the config options : All work directories are kept. Add seedcache to the config options: Only the chroot (build) directory is saved. Neither of those 2 above options : All work directories are removed. |