Section: portage (5)
Updated: Jun 2019Index
Return to Main Contents
check-reqs.eclass - Provides a uniform way of handling ebuild which have very high build requirements
This eclass provides a uniform way of handling ebuilds which have very high
build requirements in terms of memory or disk space. It provides a function
which should usually be called during pkg_setup().
The chosen action only happens when the system's resources are detected
correctly and only if they are below the threshold specified by the package.
# need this much memory (does *not* check swap)
# need this much temporary build space
# install will need this much space in /usr
# install will need this much space in /var
If you don't specify a value for, say, CHECKREQS_MEMORY, then the test is not
These checks should probably mostly work on non-Linux, and they should
probably degrade gracefully if they don't. Probably.
0 1 2 3 4 5 6 7
Exported function running the resources checks in pkg_setup phase.
It should be run in both phases to ensure condition changes between
pkg_pretend and pkg_setup won't affect the build.
Exported function running the resources checks in pkg_pretend phase.
How much RAM is needed? Eg.: CHECKREQS_MEMORY=15M
How much diskspace is needed to build the package? Eg.: CHECKREQS_DISK_BUILD=2T
How much space in /usr is needed to install the package? Eg.: CHECKREQS_DISK_USR=15G
How much space is needed in /var? Eg.: CHECKREQS_DISK_VAR=3000M
Bo Ørsted Andresen <email@example.com>
Original Author: Ciaran McCreesh <firstname.lastname@example.org>
QA Team <email@example.com>
Please report bugs via https://bugs.gentoo.org/
- SUPPORTED EAPIS
- ECLASS VARIABLES
- REPORTING BUGS
- SEE ALSO
This document was created by
using the manual pages.
Time: 03:25:03 GMT, June 18, 2019