# ====================[ environment.conf                   ]====================
#                     [ Time-stamp: "2008-10-27 01:02:25 leycec" ]
#
# For details, see "http://paludis.pioto.org/configuration/environment.html".
#
# --------------------( WORLD                              )--------------------
# Paludis follows the Portage heuristic of recording all installed packages for
# a system in the system's "world" file, unless those packages are installed
# under the "-1" (an abbreviation for "--oneshot", which was the emerge-specific
# name for this flag) or "--preserve-world" flags; in that case, the one-shotted
# packages will not be automatically updated when the world itself is updated.
#
# To effect this, run:
#    paludis --install --preserve-world ${PACKAGE_NAME}  # or "paludis -i1"
#
# --------------------( DEPENDENCIES                       )--------------------
# To find all reverse dependencies for some package (that is, all packages
# depending on that package), run:
#    adjutrix --reverse-deps ${PACKAGE_NAME}
#
# --------------------( EBUILDS                            )--------------------
# To determine which ebuilds depend on some other ebuild, run qdepends with:
#    qdepends -a ${EBUILD_NAME}
# 
# To emerge a specific version of an ebuild, specify that "atom" with:
#    emerge '=ctags-5.5.4-r2'
#
# To emerge an ebuild you've manually edited, manually recompute the MD5
# digest for the ebuild with:
#    ebuild ${FILE}.ebuild digest
#
# To add a new ebuild for software not currently registered in the main branch
# or existing overlays, move that ebuild to an appropriate directory of:
#    /usr/local/portage/
#
# New ebuilds added to the "/usr/portage/" are deleted upon the next rsync.

# ....................{ GLOBAL                             }....................
# The location of the world file.
world="${ROOT}/var/db/pkg/world"

# Possibly-empty list of characteristics that can cause a package to be
# incompatible with Portage, but that should not cause the package to be masked,
# or * (the default) to ignore Portage compatibility entirely. Currently
# available characteristics are:
#
# eapi    | ebuilds with an EAPI that is not supported by Portage
# version | ebuilds that use Paludis-specific features of package version syntax
# format  | packages other than ebuilds
#
# Note that this does not disable cache options that would cause
# interoperability problems.
accept_breaks_portage="eapi version format"