Strict testing of build dependencies
Issue #13
duplicate
It would be pretty handy if the package build environment contained only its build dependencies and its build dependencies' runtime dependencies.
For example, say I wanted to build app-misc/foo. Portage might:
- Look at app-misc/foo's build dependencies
- For each build dependency,
- run
equery f "${build_dep}"
and add the results to a file list. - look at the build dependency's runtime dependency
- For each runtime dependency
- run
equery f "${runtime_dep}"
and add the results to the file list - (Recurse through runtime dependencies)
- run
- run
- Construct a filesystem view for further build effort that, at least initially, presents only the files in the file list.
(To cope with circular dependencies, at some stage a set of bootstrap files will be necessary.)
This would force consistent build failures anywhere parallel emerge is subject to a race condition.
Comments (2)
-
-
- changed status to duplicate
Duplicate of #5.
- Log in to comment
This will be done in a separate project, as a replacement sandbox that can easily be configured such that only certain programs are allowed access to certain files. Switching to that alternate sandbox will be handled in #5, so marking this as a duplicate of that.