/etc/portage/bashrc

From Gentoo Wiki
< /etc‎ | portage(Redirected from Bashrc)
Jump to:navigation Jump to:search
Not to be confused with the ".bashrc" Bash configuration file.


The /etc/portage/bashrc file is a global bashrc file referenced by Portage. It is similar to the bashrc files under /etc/portage/env/, except that it's sourced for every package. It can either be used to setup a global environment common to all ebuilds, or as an alternative to the /etc/portage/env files (allowing Portage administrators to handle all the necessary conditional code manually), or to set up ebuild phase hooks (to perform specific actions at various stages of package installation, updates, or removal).

Hooks

In order to execute manually-specified code during an ebuild, there are two distinct ways to hook into the ebuild process: via hook functions, and via environment variables.

In the context of /etc/portage/bashrc, hook functions should be used, as this file will be sourced multiple times during the build - at least once per phase, and several other times as well. Importantly:

Important
Do not rely on use of the EBUILD_PHASE or EBUILD_PHASE_FUNC variables. Their value in global scope is not supposed to be the name of a phase - refer to bug #908552.

Execution order

The global bashrc isn't sourced for the first time until after dependency resolution. If run with --ask, bashrc is sourced for the first time shortly after interactive confirmation. Therefore, it isn't a complete replacement for the global make.conf. Anything that must be in the environment immediately - such as USE flags, FEATURES, etc. - can't be set by bashrc The Portage documentation doesn't provide a complete list of contradictions, so be careful.

Phase names

The phase names used in hook functions and in the EBUILD_PHASE_FUNC variable are:

  • pkg_setup
  • src_unpack
  • src_prepare
  • src_configure
  • src_compile
  • src_test
  • src_install
  • pkg_preinst
  • pkg_prerm
  • pkg_postrm
  • pkg_postinst

Hook functions

Portage automatically calls certain functions inside /etc/portage/bashrc if they are present. In particular, it calls functions with the name structure {pre_,post_}stage_name: for example, the pre_pkg_setup function will get called just before the pre_pkg_setup phase:

FILE /etc/portage/bashrc
function pre_pkg_setup() {
  echo "your code here"
}

Two additional hook functions are also available: register_die_hook, called when an ebuild fails; and register_success_hook, called when an ebuild is successfully merged, whose usages slightly differ from each other:

FILE /etc/portage/bashrc
register_success_hook mySuccessHook
function mySuccessHook {
    echo "success!"
}

register_die_hook myDieHook
function myDieHook {
    echo "failure!"
}

Note, however, that only an ebuild that is emerged flawlessly is considered a sufficient success to call the registered 'success' function(s). For example, a file collision during a build is enough for the function(s) not to be called, even though the rest of the emerge process was successful.

Warning
Defining a function without a pre_ or post_ prefix, e.g. a function named pkg_postinst, would override the default expected eclass implementations.

EBUILD_PHASE_FUNC and EBUILD_PHASE

During the ebuild process, the EBUILD_PHASE_FUNC variable is set to the phase names described in the "Phase names" section above.

Additionally, during the ebuild process, the EBUILD_PHASE variable gets set to the following values:

  • clean
  • setup
  • unpack
  • prepare
  • configure
  • compile
  • test
  • install
  • instprep
  • preinst
  • prerm
  • cleanrm
  • postinst
  • clean

Available environment variables

Portage doesn't save the initial environment prior to being mangled by Portage's global make.defaults and make.globals. Therefore, there is no direct way of determining whether an environment variable was supplied by the user (e.g. CFLAGS) or set by Portage, so it can't be guaranteed using the environment by bashrc to control behavior.

Variables available for reading in the environment of a bashrc script include:

Name Description
CATEGORY Package's category, e.g. app-editors
CFLAGS Flags for ${CC}
COMMON_FLAGS Flags common to ${CC} and ${CXX}
CXXFLAGS Flags for ${CXX}
D Path to the temporary install directory, e.g. ${PORTAGE_BUILDDIR}/image
LDFLAGS Flags for the compiler driver to pass to its linker
MAKEOPTS Flags for parallel make
P Package name and version (excluding revision, if any), e.g. vim-6.3
PF Full package name, ${PN}-${PVR}, e.g. vim-6.3-r1
PN Package name, e.g. vim
PR Package revision, or r0 if no revision exists
PV Package version (excluding revision, if any), e.g. 6.3
PVR Package version and revision (if any), e.g. 6.3, 6.3-r1
S Path to the temporary build directory, used by src_compile and src_install
T Path to a temporary directory which may be used by the ebuild, e.g. ${PORTAGE_BUILDDIR}/temp

See also

Retrieved from "https://wiki.gentoo.org/index.php?title=/etc/portage/bashrc&oldid=1315858"