ebuild man page

The ebuild(1) program accepts a single ebuild script as an argument. This script contains variables and commands that specify how to download, unpack, patch, compile, install and merge a particular software package from its original sources. In addition to all of this, the ebuild script can also contain pre/post install/remove commands, as required. All ebuild scripts are written in bash.

A depend atom is simply a dependency that is used by portage when calculating relationships between packages. Please note that if the atom has not already been emerged, then the latest version available is matched.

Atom Bases

The base atom is just a full category/packagename.

Examples:

sys-apps/sed
sys-libs/zlib
net-misc/dhcp

Atom Versions

It is nice to be more specific and say that only certain versions of atoms are acceptable. Note that versions must be combined with a prefix (see below). Hence you may add a version number as a postfix to the base.

Examples:

sys-apps/sed-4.0.5
sys-libs/zlib-1.1.4-r1
net-misc/dhcp-3.0_p2

Versions are normally made up of two or three numbers separated by periods, such as 1.2 or 4.5.2. This string may be followed by a character such as 1.2a or 4.5.2z. Note that this letter is not meant to indicate alpha, beta, etc... status. For that, use the optional suffix; either _alpha, _beta, _pre (pre-release), _rc (release candidate), or _p (patch). This means for the 3rd pre-release of a package, you would use something like 1.2_pre3. The suffixes here can be arbitrarily chained without limitation.

Atom Prefix Operators [> >= = <= <]

Sometimes you want to be able to depend on general versions rather than specifying exact versions all the time. Hence we provide standard boolean operators:

Now to get even fancier, we provide the ability to define blocking packages and version range matching. Also note that these extended prefixes/postfixes may be combined in any way with the atom classes defined above.

~

means match any revision of the base version specified. So in the example below, we would match versions '1.0.2a', '1.0.2a-r1', '1.0.2a-r2', etc...

Example:

~net-libs/libnet-1.0.2a

!

means block packages from being installed at the same time.

Example:

!app-text/dos2unix

!!

means block packages from being installed at the same time and explicitly disallow them from being temporarily installed simultaneously during a series of upgrades. This syntax is supported beginning with EAPI 2.

Example:

!!<sys-apps/portage-2.1.4_rc1

*

means match any version of the package so long as the specified base is matched. So with a version of '2*', we can match '2.1', '2.2', '2.2.1', etc... and not match version '1.0', '3.0', '4.1', etc... The version part that comes before the '*' must be a valid version in the absence of the '*'. For example, '2' is a valid version and '2.' is not. Therefore, '2*' is allowed and '2.*' is not.

Examples:

=dev-libs/glib-2*
!=net-fs/samba-2*

Atom Slots

Beginning with EAPI 1, any atom can be constrained to match a specific SLOT. This is accomplished by appending a colon followed by a SLOT:

Beginning with EAPI 5, slot operator dependency consists of a colon followed by one of the following operators:

*

Indicates that any slot value is acceptable. In addition, for runtime dependencies, indicates that the package will not break if the matched package is uninstalled and replaced by a different matching package in a different slot.

Examples:

dev-libs/icu:*
dev-lang/perl:*
dev-libs/glib:*

=

Indicates that any slot value is acceptable. In addition, for runtime dependencies, indicates that the package will break unless a matching package with slot and sub-slot equal to the slot and sub-slot of the best installed version at the time the package was installed is available.

Examples:

dev-libs/icu:=
dev-lang/perl:=
dev-libs/glib:=

slot=

Indicates that only a specific slot value is acceptable, and otherwise behaves identically to the plain equals slot operator.

Examples:

dev-libs/icu:0=
dev-lang/perl:0=
dev-libs/glib:2=

To implement the equals slot operator, the package manager will need to store the slot/sub-slot pair of the best installed version of the matching package. This syntax is only for package manager use and must not be used by ebuilds. The package manager may do this by inserting the appropriate slot/sub-slot pair between the colon and equals sign when saving the package's dependencies. The sub-slot part must not be omitted here (when the SLOT variable omits the sub-slot part, the package is considered to have an implicit sub-slot which is equal to the regular slot).

Beginning with EAPI 2, any atom can be constrained to match specific USE flag settings. When used together with SLOT dependencies, USE dependencies appear on the right hand side of SLOT dependencies.

Unconditional USE Dependencies

Example

Meaning

foo[bar]

foo must have bar enabled

foo[bar,baz]

foo must have both bar and baz enabled

foo[-bar,baz]

foo must have bar disabled and baz enabled

Conditional USE Dependencies

Compact Form

Equivalent Expanded Form

foo[bar?]

bar? ( foo[bar] ) !bar? ( foo )

foo[!bar?]

bar? ( foo ) !bar? ( foo[-bar] )

foo[bar=]

bar? ( foo[bar] ) !bar? ( foo[-bar] )

foo[!bar=]

bar? ( foo[-bar] ) !bar? ( foo[bar] )

Atom USE defaults

Beginning with EAPI 4, USE dependencies may specify default assumptions about values for flags that may or may not be missing from the IUSE of the matched package. Such defaults are specified by immediately following a flag with either (+) or (-). Use (+) to behave as if a missing flag is present and enabled, or (-) to behave as if it is present and disabled:

Examples:

media-video/ffmpeg[threads(+)]
media-video/ffmpeg[-threads(-)]

Dynamic Dependencies

Sometimes programs may depend on different things depending on the USE variable. Portage offers a few options to handle this. Note that when using the following syntaxes, each case is considered as 1 Atom in the scope it appears. That means that each Atom both conditionally include multiple Atoms and be nested to an infinite depth.

usevar? ( Atom )

To include the jpeg library when the user has jpeg in USE, simply use the following syntax:

jpeg? ( media-libs/jpeg )

!usevar? ( Atom )

If you want to include a package only if the user does not have a certain option in their USE variable, then use the following syntax:

!nophysfs? ( dev-games/physfs )

This is often useful for those times when you want to want to add optional support for a feature and have it enabled by default.

usevar? ( Atom if true ) !usevar? ( Atom if false )

For functionality like the tertiary operator found in C you must use two statements, one normal and one inverted. If a package uses GTK2 or GTK1, but not both, then you can handle that like this:

gtk2? ( =x11-libs/gtk+-2* ) !gtk2? ( =x11-libs/gtk+-1* )

That way the default is the superior GTK2 library.

|| ( Atom Atom ... )

When a package can work with a few different packages but a virtual is not appropriate, this syntax can easily be used.

Example:

|| (
app-games/unreal-tournament
app-games/unreal-tournament-goty
)

Here we see that unreal-tournament has a normal version and it has a goty version. Since they provide the same base set of files, another package can use either. Adding a virtual is inappropriate due to the small scope of it.

Another good example is when a package can be built with multiple video interfaces, but it can only ever have just one.

Here only one of the packages will be chosen, and the order of preference is determined by the order in which they appear. So sdl has the best chance of being chosen, followed by svga, then opengl, then ggi, with a default of X if the user does not specify any of the previous choices.

Note that if any of the packages listed are already merged, the package manager will use that to consider the dependency satisfied.

Portage supports cross-compilation into a subdirectory specified by ROOT.

Host

Host in this context means the platform hosting the build process, i.e. what autotools calls CBUILD. Its packages are contained in the root of the filesystem ("/").

If ROOT is "/", all dependency types will be installed there. Otherwise, for EAPIs that support HDEPEND (experimental EAPI 5-hdepend), only HDEPEND is installed into "/". For EAPIs that do not support HDEPEND, the behaviour is controlled by the --root-deps flag to emerge(1), defaulting to install only DEPEND into the host.

Target

Target refers to the platform that the package will later run on, i.e. what autotools calls CHOST. The directory housing this system is specified by ROOT. If it is different from "/", i.e. host and target are not the same, this variable contains the path to the directory housing the target system.

For EAPIs that support HDEPEND (experimental EAPI 5-hdepend), DEPEND, RDEPEND, and PDEPEND list the target dependencies, i.e. those to be installed into ROOT. For EAPIs that do not support HDEPEND, the emerge(1) flag --root-deps controls what the package manager installs there. Without it, emerge defaults to install only runtime dependencies (i.e. RDEPEND and PDEPEND) into ROOT.

See section Variables for more information about the DEPEND, RDEPEND and HDEPEND variables.

The targetroot USE flag

For EAPIs that support the "targetroot" USE flag, that flag is automatically enabled by the package manager if host and target system are not the same, i.e. if the ROOT is not "/". This is necessary where the package to be built needs an executable copy of itself during the build process. A known example is dev-lang/python, which needs to run a Python interpreter during compilation.

- Variables defined in make.conf(5) are available for use in ebuilds (except Portage-specific variables, which might be not supported by other package managers).- When assigning values to variables in ebuilds, you cannot have a space between the variable name and the equal sign.- Variable values should only contain characters that are members of the ascii(7) character set. This requirement is mandated by GLEP 31.

Beginning with EAPI 3, contains the offset that this Portage was configured for during installation. The offset is sometimes necessary in an ebuild or eclass, and is available in such cases as ${EPREFIX}. EPREFIX does not contain a trailing slash, therefore an absent offset is represented by the empty string. Do not modify this variable.

Contains the path to the temporary build directory. This variable is used by the functions src_compile and src_install. Both are executed with S as the current directory. This variable may be modified to match the extraction directory of a tarball for the package.

Contains the path to the temporary install directory. Every write operation that does not involve the helper tools and functions (found below) should be prefixed with ${D}. Beginning with EAPI 3, the offset prefix often needs to be taken into account here, for which the variable ${ED} is provided (see below). Do not modify this variable.

Beginning with EAPI 3, contains the path "${D%/}${EPREFIX}/" for convenience purposes. For EAPI values prior to EAPI 3 which do not support ED, helpers use D where they would otherwise use ED. Do not modify this variable.

Sonames and file paths matched by these fnmatch patterns will be excluded during genertion of PROVIDES metadata (see portage(5)). Patterns are delimited by whitespace, and it is possible to create patterns containing quoted whitespace.

Beginning with EAPI 4, the REPLACED_BY_VERSION variable can be used in pkg_prerm and pkg_postrm to query the package version that is replacing the current package. If there is no replacement package, the variable will be empty, otherwise it will contain a single version number.

Beginning with EAPI 4, the REPLACING_VERSIONS variable can be used in pkg_pretend, pkg_setup, pkg_preinst and pkg_postinst to query the package version(s) that the current package is replacing. If there are no packages to replace, the variable will be empty, otherwise it will contain a space-separated list of version numbers corresponding to the package version(s) being replaced. Typically, this variable will not contain more than one version, but according to PMS it can contain more.

Sonames and file paths matched by these fnmatch patterns will be excluded during generation of REQUIRES metadata (see portage(5)). Patterns are delimited by whitespace, and it is possible to create patterns containing quoted whitespace.

Contains the path that portage should use as the root of the live filesystem. When packages wish to make changes to the live filesystem, they should do so in the tree prefixed by ${ROOT}. Often the offset prefix needs to be taken into account here, for which the variable ${EROOT} is provided (see below). Do not modify this variable.

Defines the ebuild API version to which this package conforms. If not defined then it defaults to "0". If portage does not recognize the EAPI value then it will mask the package and refuse to perform any operations with it since this means that a newer version of portage needs to be installed first. For maximum backward compatiblity, a package should conform to the lowest possible EAPI. Note that anyone who uses the ebuild(1) and repoman(1) commands with this package will be required to have a version of portage that recognizes the EAPI to which this package conforms.

Contains a list of URIs for the required source files. It can contain multiple URIs for a single source file. The list is processed in order if the file was not found on any of the GENTOO_MIRRORS. Beginning with EAPI 2, the output file name of a given URI may be customized with a "->" operator on the right hand side, followed by the desired output file name. All tokens, including the operator and output file name, should be separated by whitespace.

Should contain appropriate list of arches that the ebuild is know to work/not work. By default if you do not know if an ebuild runs under a particular arch simply omit that KEYWORD. If the ebuild will not work on that arch include it as -ppc for example. If the ebuild is being submitted for inclusion, it must have ~arch set for architectures where it has been PROVEN TO WORK. (Packages KEYWORDed this way may be unmasked for testing by setting ACCEPT_KEYWORDS="~arch" on the command line, or in make.conf(5)) For an authoritative list please review /usr/portage/profiles/arch.list. Please keep this list in alphabetical order.

This sets the SLOT for packages that may need to have multiple versions co-exist. By default you should set SLOT="0". If you are unsure, then do not fiddle with this until you seek some guidance from some guru. This value should NEVER be left undefined.

Beginning with EAPI 5, the SLOT variable may contain an optional sub-slot part that follows the regular slot and is delimited by a / character. The sub-slot must be a valid slot name. The sub-slot is used to represent cases in which an upgrade to a new version of a package with a different sub-slot may require dependent packages to be rebuilt. When the sub-slot part is omitted from the SLOT definition, the package is considered to have an implicit sub-slot which is equal to the regular slot. Refer to the Atom Slot Operators section for more information about sub-slot usage.

This should be a space delimited list of licenses that the package falls under. This _must_ be set to a matching license in /usr/portage/licenses/. If the license does not exist in portage yet, you must add it first.

This should be a list of any and all USE flags that are leveraged within your build script. The only USE flags that should not be listed here are arch related flags (see KEYWORDS). Beginning with EAPI 1, it is possible to prefix flags with + or - in order to create default settings that respectively enable or disable the corresponding USE flags. For details about USE flag stacking order, refer to the USE_ORDER variable in make.conf(5). Given the default USE_ORDER setting, negative IUSE default settings are effective only for negation of repo-level USE settings, since profile and user configuration settings override them.

This should contain a list of all packages that are required for the program to compile (aka buildtime dependencies). These are usually libraries and headers.

Starting from experimental EAPI 5-hdepend, tools should go into the HDEPEND variable instead, as DEPEND will only be installed into the target system and hence cannot be executed in a cross-compile setting. (See section Cross-compilation for more information.)

This should contain a list of all packages that are required to be executable during compilation of this program (aka host buildtime dependencies). These are usually tools, like interpreters or (cross-)compilers.

This variable is new in experimental EAPI 5-hdepend and will be installed into the host system. (See section Cross-compilation for more information.)

This should be a space delimited list of portage features to restrict. You may use conditional syntax to vary restrictions as seen above in DEPEND.

binchecks

Disable all QA checks for binaries. This should ONLY be used in packages for which binary checks make no sense (linux-headers and kernel-sources, for example, can safely be skipped since they have no binaries). If the binary checks need to be skipped for other reasons (such as proprietary binaries), see the QA CONTROL VARIABLES section for more specific exemptions.

bindist

Distribution of built packages is restricted.

fetch

like mirror but the files will not be fetched via SRC_URI either.

installsources

Disables installsources for specific packages. This is for packages with binaries that are not compatible with debugedit.

mirror

files in SRC_URI will not be downloaded from the GENTOO_MIRRORS.

preserve-libs

Disables preserve-libs for specific packages. Note than when a package is merged, RESTRICT=preserve-libs applies if either the new instance or the old instance sets RESTRICT=preserve-libs.

primaryuri

fetch from URIs in SRC_URI before GENTOO_MIRRORS.

splitdebug

Disables splitdebug for specific packages. This is for packages with binaries that trigger problems with splitdebug, such as file-collisions between symlinks in /usr/lib/debug/.build-id (triggered by bundled libraries).

This variable should only be used when a package provides a virtual target. For example, blackdown-jdk and sun-jdk provide virtual/jdk. This allows for packages to depend on virtual/jdk rather than on blackdown or sun specifically.

Beginning with EAPI 4, an array or space-delimited list of documentation files for the default src_install function to install using dodoc. If undefined, a reasonable default list is used. See the documentation for src_install below.

Several QA variables are provided which allow an ebuild to manipulate some of the QA checks performed by portage. Use of these variables in ebuilds should be kept to an absolute minimum otherwise they defeat the purpose of the QA checks, and their use is subject to agreement of the QA team. They are primarily intended for use by ebuilds that install closed-source binary objects that cannot be altered.

Note that objects that violate these rules may fail on some architectures.

QA_PREBUILT

This should contain a list of file paths, relative to the image directory, of files that are pre-built binaries. Paths listed here will be appended to each of the QA_* variables listed below. The paths may contain fnmatch-like patterns which will be internally translated to regular expressions for the QA_* variables that support regular expressions instead of fnmatch patterns. The translation mechanism simply replaces "*" with ".*".

QA_TEXTRELS

This variable can be set to a list of file paths, relative to the image directory, of files that contain text relocations that cannot be eliminated. The paths may contain fnmatch patterns.

This variable is intended to be used on closed-source binary objects that cannot be altered.

QA_EXECSTACK

This should contain a list of file paths, relative to the image directory, of objects that require executable stack in order to run. The paths may contain fnmatch patterns.

This variable is intended to be used on objects that truly need executable stack (i.e. not those marked to need it which in fact do not).

QA_WX_LOAD

This should contain a list of file paths, relative to the image directory, of files that contain writable and executable segments. These are rare. The paths may contain fnmatch patterns.

QA_FLAGS_IGNORED

This should contain a list of file paths, relative to the image directory, of files that do not contain .GCC.command.line sections or contain .hash sections. The paths may contain regular expressions with escape-quoted special characters.

This variable is intended to be used on files of binary packages which ignore CFLAGS, CXXFLAGS, FFLAGS, FCFLAGS, and LDFLAGS variables.

QA_MULTILIB_PATHS

This should contain a list of file paths, relative to the image directory, of files that should be ignored for the multilib-strict checks. The paths may contain regular expressions with escape-quoted special characters.

QA_PRESTRIPPED

This should contain a list of file paths, relative to the image directory, of files that contain pre-stripped binaries. The paths may contain regular expressions with escape-quoted special characters.

QA_SONAME

This should contain a list of file paths, relative to the image directory, of shared libraries that lack SONAMEs. The paths may contain regular expressions with escape-quoted special characters.

QA_SONAME_NO_SYMLINK

This should contain a list of file paths, relative to the image directory, of shared libraries that have SONAMEs but should not have a corresponding SONAME symlink in the same directory. The paths may contain regular expressions with escape-quoted special characters.

QA_AM_MAINTAINER_MODE

This should contain a list of lines containing automake missing --run commands. The lines may contain regular expressions with escape-quoted special characters.

QA_CONFIGURE_OPTIONS

This should contain a list of configure options which trigger warnings about unrecognized options. The options may contain regular expressions with escape-quoted special characters.

QA_DT_NEEDED

This should contain a list of file paths, relative to the image directory, of shared libraries that lack NEEDED entries. The paths may contain regular expressions with escape-quoted special characters.

QA_DESKTOP_FILE

This should contain a list of file paths, relative to the image directory, of desktop files which should not be validated. The paths may contain regular expressions with escape-quoted special characters.

Inherit is portage's maintenance of extra classes of functions that are external to ebuilds and provided as inheritable capabilities and data. They define functions and set data types as drop-in replacements, expanded, and simplified routines for extremely common tasks to streamline the build process. Call to inherit cannot depend on conditions which can vary in given ebuild. Specification of the eclasses contains only their name and not the .eclass extension. Also note that the inherit statement must come before other variable declarations unless these variables are used in global scope of eclasses.

Beginning with EAPI 4, this function can be defined in order to check that miscellaneous requirements are met. It is called as early as possible, before any attempt is made to satisfy dependencies. If the function detects a problem then it should call eerror and die. The environment (variables, functions, temporary directories, etc..) that is used to execute pkg_pretend is not saved and therefore is not available in phases that execute afterwards.

This function will be executed when the files in SRC_URI cannot be fetched for any reason. If you turn on fetch in RESTRICT, this is useful for displaying information to the user on *how* to obtain said files. All you have to do is output a message and let the function return. Do not end the function with a call to die.

This function is used to unpack all the sources in A to WORKDIR. If not defined in the ebuild script it calls unpack ${A}. Any patches and other pre configure/compile modifications should be done here.Initial working directory: $WORKDIR

Run all package specific test cases. The default is to run ´emake check´ followed ´emake test´. Prior to EAPI 5, the default src_test implementation will automatically pass the -j1 option as the last argument to emake, and beginning with EAPI 5 it will allow the tests to run in parallel.Initial working directory: $S

All modifications required on the live-filesystem before and after the package is merged should be placed here. Also commentary for the user should be listed here as it will be displayed last.Initial working directory: $PWD

pkg_prerm pkg_postrm

Like the pkg_*inst functions but for unmerge.Initial working directory: $PWD

Calls the default phase function implementation for the currently executing phase. This function is supported beginning with EAPI 2.

default_*

Beginning with EAPI 2, the default pkg_nofetch and src_* phase functions are accessible via a function having a name that begins with default_ and ends with the respective phase function name. For example, a call to a function with the name default_src_compile is equivalent to a call to the default src_compile implementation.

Checks the value of the shell's PIPESTATUS array variable, and if any component is non-zero (indicating failure), calls die with reason as a failure message.

die[reason]

Causes the current emerge process to be aborted. The final display will include reason.

Beginning with EAPI 4, all helpers automatically call die whenever some sort of error occurs. Helper calls may be prefixed with the nonfatal helper in order to prevent errors from being fatal.

nonfatal<helper>

Execute helper and do not call die if it fails. The nonfatal helper is available beginning with EAPI 4.

use<USE item>

If USE item is in the USE variable, the function will silently return 0 (aka shell true). If USE item is not in the USE variable, the function will silently return 1 (aka shell false). usev is a verbose version of use.

Example:

if use gnome ; then
guiconf="--enable-gui=gnome --with-x"
elif use gtk ; then
guiconf="--enable-gui=gtk --with-x"
elif use X ; then
guiconf="--enable-gui=athena --with-x"
else
# No gui version will be built
guiconf=""
fi

If USE flag is set, echo [true output][true suffix] (defaults to "yes"), otherwise echo [false output][false suffix] (defaults to "no"). The usex helper is available beginning with EAPI 5.

use_with<USE item> [configure name] [configure opt]

Useful for creating custom options to pass to a configure script. If USE item is in the USE variable and a configure opt is specified, then the string --with-[configure name]=[configure opt] will be echoed. If configure opt is not specified, then just --with-[configure name] will be echoed. If USE item is not in the USE variable, then the string --without-[configure name] will be echoed. If configure name is not specified, then USE item will be used in its place. Beginning with EAPI 4, an empty configure opt argument is recognized. In EAPI 3 and earlier, an empty configure opt argument is treated as if it weren't provided.

Examples:

USE="opengl"
myconf=$(use_with opengl)
(myconf now has the value "--with-opengl")
USE="jpeg"
myconf=$(use_with jpeg libjpeg)
(myconf now has the value "--with-libjpeg")
USE=""
myconf=$(use_with jpeg libjpeg)
(myconf now has the value "--without-libjpeg")
USE="sdl"
myconf=$(use_with sdl SDL all-plugins)
(myconf now has the value "--with-SDL=all-plugins")

use_enable<USE item> [configure name] [configure opt]

Same as use_with above, except that the configure options are --enable- instead of --with- and --disable- instead of --without-. Beginning with EAPI 4, an empty configure opt argument is recognized. In EAPI 3 and earlier, an empty configure opt argument is treated as if it weren't provided.

has<item> <item list>

If item is in item list, then has returns 0. Otherwise, 1 is returned. There is another version, hasv, that will conditionally echo item.The item list is delimited by the IFS variable. This variable has a default value of ' ', or a space. It is a bash(1) setting.

hasv<item> <item list>

Like has, but also echoes item when has returns true.

has_version[--host-root] <category/package-version>

Check to see if category/package-version is installed on the system. The parameter accepts all values that are acceptable in the DEPEND variable. The function returns 0 if category/package-version is installed, 1 otherwise. Beginning with EAPI 5, the --host-root option may be used in order to cause the query to apply to the host root instead of ${ROOT}.

best_version[--host-root] <package name>

This function will look up package name in the database of currently installed programs and echo the "best version" of the package that is currently installed. Beginning with EAPI 5, the --host-root option may be used in order to cause the query to apply to the host root instead of ${ROOT}.

Example:

VERINS="$(best_version net-ftp/glftpd)"
(VERINS now has the value "net-ftp/glftpd-1.27" if glftpd-1.27 is installed)

Same as elog, but should be used when the message isn't important to the user (like progress or status messages during the build process).

elog"informative message"

If you need to display a message that you wish the user to read and take notice of, then use elog. It works just like echo(1), but adds a little more to the output so as to catch the user's eye. The message will also be logged by portage for later review.

ewarn"warning message"

Same as einfo, but should be used when showing a warning to the user.

eqawarn"QA warning message"

Same as einfo, but should be used when showing a QA warning to the user.

eerror"error message"

Same as einfo, but should be used when showing an error to the user.

ebegin"helpful message"

Like einfo, we output a helpful message and then hint that the following operation may take some time to complete. Once the task is finished, you need to call eend.

eend<status> ["error message"]

Followup the ebegin message with an appropriate "OK" or "!!" (for errors) marker. If status is non-zero, then the additional error message is displayed.

Note that the EXTRA_ECONF is for users only, not for ebuild writers. If you wish to pass more options to configure, just pass the extra arguments to econf. Also note that econf automatically calls die if the configure script fails. Beginning with EAPI 3, econf uses the ${EPREFIX} variable which is disregarded for prior EAPI values. Beginning with EAPI 4, econf adds --disable-dependency-tracking to the arguments if the string disable-dependency-tracking occurs in the output of configure --help. Beginning with EAPI 5, econf adds disable-silent-rules to the arguments if the string disable-silent-rules occurs in the output of configure --help.

emake[make options]

This must be used in place of `make` in ebuilds. Performs `${MAKE:-make} ${MAKEOPTS} make options ${EXTRA_EMAKE}`, and calls `die` automatically starting with EAPI 4.

The MAKEOPTS variable is set by the user so they can enable features such as parallel builds; see make.conf(5) for more details.

The EXTRA_EMAKE knob is portage feature so developers can override things while debugging ebuilds; it is not part of any EAPI specification.

***WARNING***You must make sure your build is happy with parallel makes (make -j2). It should be tested thoroughly as parallel makes are notorious for failing _sometimes_ but not always. If you determine that your package fails to build in parallel, and you are unable to resolve the issue, then you should run `emake -j1` explicitly. This is a last resort however as it can significantly slow down builds on systems with lots of processors.

Please do not use this in place of 'emake install DESTDIR=${D}'. That is the preferred way of installing make-based packages. Also, do not utilize the EXTRA_EINSTALL variable since it is for users.

prepall

prepalldocs

prepallinfo

prepallman

prepallstrip

Useful for when a package installs into ${D} via scripts (i.e. makefiles). If you want to be sure that libraries are executable, aclocal files are installed into the right place, doc/info/man files are all compressed, and that executables are all stripped of debugging symbols, then use these suite of functions.

Strips all executable files of debugging symboles. This includes libraries.

prepinfo[dir]

prepman[dir]

prepstrip[dir]

Similar to the prepall functions, these are subtle in their differences.

prepinfo:

If a dir is not specified, then prepinfo will assume the dir usr. prepinfo will then compress all the files in ${ED}/dir/info.

prepman:

If a dir is not specified, then prepman will assume the dir usr. prepman will then compress all the files in ${ED}/dir/man/*/.

prepstrip:

All the files found in ${ED}/dir will be stripped. You may specify multiple directories.

docompress[-x] <path> [list of more paths]

Beginning with EAPI 4, the docompress helper is used to manage lists of files to be included or excluded from optional compression. If the first argument is -x, add each of its subsequent arguments to the exclusion list. Otherwise, add each argument to the inclusion list. The inclusion list initially contains /usr/share/doc, /usr/share/info, and /usr/share/man. The exclusion list initially contains /usr/share/doc/${PF}/html.

The optional compression shall be carried out after src_install has completed, and before the execution of any subsequent phase function. For each item in the inclusion list, pretend it has the value of the D variable prepended, then:

If it is a directory, act as if every file or directory immediately under this directory were in the inclusion list.

If the item is a file, it may be compressed unless it has been excluded as described below.

If the item does not exist, it is ignored.

Whether an item is to be excluded is determined as follows: For each item in the exclusion list, pretend it has the value of the D variable prepended, then:

If it is a directory, act as if every file or directory immediately under this directory were in the exclusion list.

If the item is a file, it shall not be compressed.

If the item does not exist, it is ignored.

dosed"s:orig:change:g" <filename>

Beginning with EAPI 4, the dosed helper no longer exists. Ebuilds should call sed(1) directly (and assume that it is GNU sed).

Performs sed in place on filename inside ${ED}. If no expression is given then "s:${D}::g" is used as the default expression. Note that this expression does NOT use the offset prefix.'dosed "s:/usr/local:/usr:g" /usr/bin/some-script' runs sed on ${ED}/usr/bin/some-script

dodir<path> [more paths]

Creates directories inside of ${ED}.'dodir /usr/lib/apache' creates ${ED}/usr/lib/apache. Note that the do* functions will run dodir for you.

Can be used to define options for the install function used in the dolib functions. The default is -m0644.

doman[-i18n=<locale>] <man-page> [list of more man-pages]

Installs manual-pages into /usr/share/man/man[0-9n] depending on the manual file ending. The files are compressed if they are not already. You can specify locale-specific manpages with the -i18n option. Then the man-page will be installed into /usr/share/man/<locale>/man[0-9n]. Beginning with EAPI 2, a locale-specific manpage which contains a locale in the file name will be installed in /usr/share/man/<locale>/man[0-9n], with the locale portion of the file name removed, and the -i18n option has no effect. For example, with EAPI 2, a manpage named foo.<locale>.1 will be installed as /usr/share/man/<locale>/man1/foo.1. Beginning with EAPI 4, the -i18n option takes precedence over the locale suffix of the file name.

Installs the given header files into /usr/include/, by default with file mode 0644 (this can be overridden with the insopts function). Setting -r sets recursive. The doheader helper is available beginning with EAPI 5.

Can be used to define options for the install function used in doexe. The default is -m0755.

doexe<executable> [list of more executables]

Installs executables into the path controlled by exeinto. This function uses install(1). Creates all necessary dirs.

docinto[path]

Sets the subdir used by dodoc and dohtml when installing into the document tree (based in /usr/share/doc/${PF}/). Default is no subdir, or just "".

dodoc[-r] <document> [list of more documents]

Installs a document or a list of documents into /usr/share/doc/${PF}/<docinto path>. Documents are marked for compression. Creates all necessary dirs. Beginning with EAPI 4, there is support for recursion, enabled by the new -r option.

newbin<old file> <new filename>

newsbin<old file> <new filename>

newinitd<old file> <new filename>

newconfd<old file> <new filename>

newenvd<old file> <new filename>

newlib.so<old file> <new filename>

newlib.a<old file> <new filename>

newman<old file> <new filename>

newins<old file> <new filename>

newexe<old file> <new filename>

newdoc<old file> <new filename>

All these functions act like the do* functions, but they only work with one file and the file is installed as [new filename]. Beginning with EAPI 5, standard input is read when the first parameter is - (a hyphen).