EBUILD(1) Portage EBUILD(1) | | |
NAME
ebuild - a low level interface to the Portage system | | |
SYNOPSIS
ebuild file command [command]... | | |
DESCRIPTION
The ebuild program is a direct interface to the Portage system. It allows for direct action upon an ebuild with specific
subcommands or groups of commands to perform in a specific ebuild's context and functions. Accepting an ebuild script
and one or more commands as arguments, the ebuild program parses the ebuild script and executes the specified commands.
Commands exist to fetch sources, unpack sources, compile sources, install object files into a temporary directory
"image", merge the image to the local filesystem, create a bzipped tarball package out of the image, and more. | | |
FILE
This must be a valid ebuild script. For further information read ebuild(5). | | |
COMMANDS
By default, portage will execute all the functions in order up to the one actually specified. For example, simply issu‐
ing the command compile will trigger the functions before it to also be run (such as setup and unpack). If you wish to
only have the specified command run, then you should use the noauto option in the FEATURES environment variable. See the
make.conf(5) man page for more information. | | |
help Shows a condensed form of this man page along with a lot of package specific information. | | |
setup Runs all package-specific setup actions and exotic system checks. | | |
clean Cleans the temporary build directory that Portage has created for this particular ebuild file. The temporary
build directory normally contains the extracted source files as well as a possible "install image" (all the files
that will be merged to the local filesystem or stored in a package). The location of the build directory is set
by the BUILD_PREFIX variable. For information on what this variable is, run emerge [-v] info, or to override this
variable, see make.conf(5). | | |
