NAME

SYNOPSIS

emerge

[options] [action] [ebuild | tbz2file | file | @set | atom] ...

emerge

--sync | --version

emerge

--info [atom]

emerge

--search somestring

emerge

--help [--verbose]

DESCRIPTION

EBUILDS, TBZ2S, SETS AND ATOMS

ebuild

An ebuild must be, at a minimum, a valid Portage package directory name without a version or category, such as portage or python. Both categories and version numbers may be used in addition, such as sys-apps/portage or =python-2.2.1-r2. emerge ignores a trailing slash so that filename completion can be used. The ebuild may also be an actual filename, such as /usr/portage/app-admin/python/python-2.2.1-r2.ebuild. WARNING: The implementation of emerge /path/to/ebuild is broken and so this syntax shouldn't be used.

tbz2file

A tbz2file must be a valid .tbz2 created with ebuild <package>-<version>.ebuild package or emerge --buildpkg [category/]<package> or quickpkg /var/db/pkg/<category>/<package>.

file

A file must be a file or directory that has been installed by one or more packages. For directories that are owned by multiple packages, all owning packages to be selected. See the portageq(1) owners command if you would like to query the owners of one or more files or directories.

set

A set is a convenient shorthand for a large group of packages. Three sets are currently always available: selected, system and world. selected contains the user-selected "world" packages that are listed in /var/lib/portage/world. system refers to a set of packages deemed necessary for your system to run properly. world encompasses both the selected and system sets. [See FILES below for more information.] Note that a set is generally used in conjunction with --update. When used as arguments to emerge sets have to be prefixed with @ to be recognized. Use the --list-sets action to display a list of available package sets.

atom

An atom describes bounds on a package that you wish to install. See portage(5) for the details on atom syntax. For example, >=dev-lang/python-2.2.1-r2 matches the latest available version of Python greater than or equal to 2.2.1-r2. Similarly, <dev-lang/python-2.0 matches the latest available version of Python before 2.0. Note that in many shells you will need to escape characters such as '<' and '='; use single- or double-quotes around the atom to get around escaping problems.

ACTIONS

No action

If no action is specified, the action is to merge in the specified packages, satisfying any dependencies that they may have. The arguments can be ebuilds, tbz2s, sets, or atoms. Note that you need to use the --usepkg option if you want to install a tbz2. The packages are added to the world file at the end, so that they are considered for later updating.

--clean

Cleans up the system by examining the installed packages and removing older packages. This is accomplished by looking at each installed package and separating the installed versions by slot. Clean will remove all but the most recently installed version in each slot. Clean should not remove unslotted packages. Note: Most recently installed means most recent, not highest version.

--config

Run package specific actions needed to be executed after the emerge process has completed. This usually entails configuration file setup or other similar setups that the user may wish to run.

--depclean (-c)

Cleans the system by removing packages that are not associated with explicitly merged packages. Depclean works by creating the full dependency tree from the @world set, then comparing it to installed packages. Packages installed, but not part of the dependency tree, will be uninstalled by depclean. See --with-bdeps for behavior with respect to build time dependencies that are not strictly required. Packages that are part of the world set will always be kept. They can be manually added to this set with emerge --noreplace <atom>. As a safety measure, depclean will not remove any packages unless *all* required dependencies have been resolved. As a consequence, it is often necessary to run emerge --update --newuse --deep @world prior to depclean.

WARNING: Inexperienced users are advised to use --pretend with this option in order to see a preview of which packages will be uninstalled. Always study the list of packages to be cleaned for any obvious mistakes. Note that packages listed in package.provided (see portage(5)) may be removed by depclean, even if they are part of the world set. Also note that depclean may break link level dependencies. Thus, it is recommended to use a tool such as revdep-rebuild(1) in order to detect such breakage.

Depclean serves as a dependency aware version of --unmerge. When given one or more atoms, it will unmerge matched packages that have no reverse dependencies. Use --depclean together with --verbose to show reverse dependencies.

--deselect[=n]

Remove atoms and/or sets from the world file. This action is implied by uninstall actions, including --depclean, --prune and --unmerge. Use --deselect=n in order to prevent uninstall actions from removing atoms from the world file.

--help (-h)

Displays help information for emerge. Adding one of the additional arguments listed above will give you more specific help information on that subject. The internal emerge help documentation is updated more frequently than this man page; check it out if you are having problems that this man page does not help resolve.

--info

Produces a list of information to include in bug reports which aids the developers when fixing the reported problem. Please include this information when submitting a bug report. Expanded output can be obtained with the --verbose option.

--list-sets

Displays a list of available package sets.

--metadata

Transfers metadata cache from ${PORTDIR}/metadata/cache/ to /var/cache/edb/dep/ as is normally done on the tail end of an rsync update using emerge --sync. This process populates the cache database that portage uses for pre-parsed lookups of package data. It does not populate cache for the overlays listed in PORTDIR_OVERLAY. In order to generate cache for overlays, use --regen. In versions of portage >=2.1.5 the --metadata action is totally unnecessary unless the user has enabled FEATURES="metadata-transfer" in make.conf(5).

--prune (-P)

WARNING: This action can remove important packages! Removes all but the highest installed version of a package from your system. Use --prune together with --verbose to show reverse dependencies or with --nodeps to ignore all dependencies.

--regen

Causes portage to check and update the dependency cache of all ebuilds in the portage tree. The cache is used to speed up searches and the building of dependency trees. This command is not recommended for rsync users as rsync updates the cache using server-side caches. If you do not know the differences between a 'rsync user' and some other user, then you are a 'rsync user' :). Rsync users should simply run emerge --sync to regenerate the cache. After a portage update, rsync users may find it convenient to run emerge --metadata to rebuild the cache as portage does at the end of a sync operation. In order to specify parallel --regen behavior, use the --jobs and --load-average options. If you would like to generate and distribute cache for use by others, use egencache(1).

--resume(-r)

Resumes the most recent merge list that has been aborted due to an error. Please note that this operation will only return an error on failure. If there is nothing for portage to do, then portage will exit with a message and a success condition. A resume list will persist until it has been completed in entirety or until another aborted merge list replaces it. The resume history is capable of storing two merge lists. After one resume list completes, it is possible to invoke --resume once again in order to resume an older list.

--search (-s)

Searches for matches of the supplied string in the portage tree. By default emerge uses a case-insensitive simple search, but you can enable a regular expression search by prefixing the search string with %. For example, emerge --search "%^kde" searches for any package whose name starts with "kde"; emerge --search "%gcc$" searches for any package that ends with "gcc"; emerge --search "office" searches for any package that contains the word "office". If you want to include the category into the search string, prepend an @: emerge --search "%@^dev-java.*jdk". If you want to search the package descriptions as well, use the --searchdesc action.

--searchdesc (-S)

Matches the search string against the description field as well as the package name. Take caution as the descriptions are also matched as regular expressions.

--sync

This updates the portage tree that is located in the directory that the PORTDIR variable refers to (default location is /usr/portage). The SYNC variable specifies the remote URI from which files will be synchronized. The PORTAGE_SYNC_STALE variable configures warnings that are shown when emerge --sync has not been executed recently.

WARNING: The emerge --sync action will modify and/or delete files located inside the directory that the PORTDIR variable refers to (default location is /usr/portage). For more information, see the PORTDIR documentation in the make.conf(5) man page.

NOTE: The emerge-webrsync program will download the entire portage tree as a tarball, which is much faster than emerge --sync for first time syncs.

--unmerge (-C)

WARNING: This action can remove important packages! Removes all matching packages. This does no checking of dependencies, so it may remove packages necessary for the proper operation of your system. Its arguments can be atoms or ebuilds. For a dependency aware version of --unmerge, use --depclean or --prune.

--version (-V)

Displays the version number of emerge.

OPTIONS

--accept-properties=ACCEPT_PROPERTIES

This option temporarily overrides the ACCEPT_PROPERTIES variable. The ACCEPT_PROPERTIES variable is incremental, which means that the specified setting is appended to the existing value from your configuration. The special -* token can be used to discard the existing configuration value and start fresh. See the MASKED PACKAGES section and make.conf(5) for more information about ACCEPT_PROPERTIES. A typical usage example for this option would be to use --accept-properties=-interactive to temporarily mask interactive packages. With default configuration, this would result in an effective ACCEPT_PROPERTIES value of "* -interactive".

--alphabetical

When displaying USE and other flag output, combines the enabled and disabled lists into one list and sorts the whole list alphabetically.

--ask (-a)

Before performing the action, display what will take place (server info for --sync, --pretend output for merge, and so forth), then ask whether to proceed with the action or abort. Using --ask is more efficient than using --pretend and then executing the same command without --pretend, as dependencies will only need to be calculated once. WARNING: If the "Enter" key is pressed at the prompt (with no other input), it is interpreted as acceptance of the first choice. Note that the input buffer is not cleared prior to the prompt, so an accidental press of the "Enter" key at any time prior to the prompt will be interpreted as a choice! Use the --ask-enter-invalid option if you want a single "Enter" key press to be interpreted as invalid input.

--ask-enter-invalid

When used together with the --ask option, interpret a single "Enter" key press as invalid input. This helps prevent accidental acceptance of the first choice. This option is intended to be set in the make.conf(5) EMERGE_DEFAULT_OPTS variable.

--autounmask[=n]

Automatically unmask packages. If any configuration changes are required, then they will be displayed after the merge list and emerge will immediately abort. If the displayed configuration changes are satisfactory, you should copy and paste them into the specified configuration file(s). Currently, this only works for unstable KEYWORDS masks, LICENSE masks, and package.use settings.

--backtrack=COUNT

Specifies an integer number of times to backtrack if dependency calculation fails due to a conflict or an unsatisfied dependency (default: '5').

--binpkg-respect-use < y | n >

Tells emerge to ignore binary packages if their use flags don't match the current configuration. (default: 'n')

--buildpkg (-b)

Tells emerge to build binary packages for all ebuilds processed in addition to actually merging the packages. Useful for maintainers or if you administrate multiple Gentoo Linux systems (build once, emerge tbz2s everywhere) as well as disaster recovery. The package will be created in the PKGDIR directory (see make.conf(5)). An alternative for already-merged packages is to use quickpkg(1) which creates a tbz2 from the live filesystem.

--buildpkgonly (-B)

Creates binary packages for all ebuilds processed without actually merging the packages. This comes with the caveat that all build-time dependencies must already be emerged on the system.

--changed-use

This is an alias for --reinstall=changed-use.

--changelog (-l)

Use this in conjunction with the --pretend option. This will show the ChangeLog entries for all the packages that will be upgraded.

--color < y | n >

Enable or disable color output. This option will override NOCOLOR (see make.conf(5)) and may also be used to force color output when stdout is not a tty (by default, color is disabled unless stdout is a tty).

--columns

Used alongside --pretend to cause the package name, new version, and old version to be displayed in an aligned format for easy cut-n-paste.

--complete-graph[=n]

This causes emerge to consider the deep dependencies of all packages from the world set. With this option enabled, emerge will bail out if it determines that the given operation will break any dependencies of the packages that have been added to the graph. Like the --deep option, the --complete-graph option will significantly increase the time taken for dependency calculations. Note that, unlike the --deep option, the --complete-graph option does not cause any more packages to be updated than would have otherwise been updated with the option disabled.

--config-root=DIR

Set the PORTAGE_CONFIGROOT environment variable.

--debug (-d)

Tells emerge to run the emerge command in --debug mode. In this mode the bash build environment will run with the -x option, causing it to output verbose debugging information to stdout. This also enables a plethora of other output (mostly dependency resolution messages).

--deep [DEPTH] (-D)

This flag forces emerge to consider the entire dependency tree of packages, instead of checking only the immediate dependencies of the packages. As an example, this catches updates in libraries that are not directly listed in the dependencies of a package. Also see --with-bdeps for behavior with respect to build time dependencies that are not strictly required.

--emptytree (-e)

Reinstalls target atoms and their entire deep dependency tree, as though no packages are currently installed. You should run this with --pretend first to make sure the result is what you expect.

--exclude ATOMS

A space separated list of package names or slot atoms. Emerge won't install any ebuild or binary package that matches any of the given package atoms.

--fail-clean[=n]

Clean up temporary files after a build failure. This is particularly useful if you have PORTAGE_TMPDIR on tmpfs. If this option is enabled, you probably also want to enable PORT_LOGDIR (see make.conf(5)) in order to save the build log.

--fetchonly (-f)

Instead of doing any package building, just perform fetches for all packages (fetch things from SRC_URI based upon USE setting).

--fetch-all-uri (-F)

Instead of doing any package building, just perform fetches for all packages (fetch everything in SRC_URI regardless of USE setting).

--getbinpkg[=n] (-g)

Using the server and location defined in PORTAGE_BINHOST (see make.conf(5)), portage will download the information from each binary package found and it will use that information to help build the dependency list. This option implies -k. (Use -gK for binary-only merging.)

--getbinpkgonly[=n] (-G)

This option is identical to -g, as above, except binaries from the remote server are preferred over local packages if they are not identical.

--ignore-default-opts

Causes EMERGE_DEFAULT_OPTS (see make.conf(5)) to be ignored.

-j [JOBS], --jobs[=JOBS]

Specifies the number of packages to build simultaneously. If this option is given without an argument, emerge will not limit the number of jobs that can run simultaneously. Also see the related --load-average option. Note that interactive packages currently force a setting of --jobs=1. This issue can be temporarily avoided by specifying --accept-properties=-interactive.

--keep-going[=n]

Continue as much as possible after an error. When an error occurs, dependencies are recalculated for remaining packages and any with unsatisfied dependencies are automatically dropped. Also see the related --skipfirst option.

--load-average=LOAD

Specifies that no new builds should be started if there are other builds running and the load average is at least LOAD (a floating-point number). This option is recommended for use in combination with --jobs in order to avoid excess load. See make(1) for information about analogous options that should be configured via MAKEOPTS in make.conf(5).

--newuse (-N)

Tells emerge to include installed packages where USE flags have changed since compilation. This option also implies the --selective option. USE flag changes include:

A USE flag was added to a package. A USE flag was removed from a package. A USE flag was turned on for a package. A USE flag was turned off for a package.

USE flags may be toggled by your profile as well as your USE and package.use settings.

--noconfmem

Causes portage to disregard merge records indicating that a config file inside of a CONFIG_PROTECT directory has been merged already. Portage will normally merge those files only once to prevent the user from dealing with the same config multiple times. This flag will cause the file to always be merged.

--nodeps (-O)

Merges specified packages without merging any dependencies. Note that the build may fail if the dependencies aren't satisfied.

--noreplace (-n)

Skips the packages specified on the command-line that have already been installed. Without this option, any packages, ebuilds, or deps you specify on the command-line will cause Portage to remerge the package, even if it is already installed. Note that Portage will not remerge dependencies by default. Also note that this option takes precedence over options such as --newuse, preventing a package from being reinstalled even though the corresponding USE flag settings may have changed.

--nospinner

Disables the spinner for the session. The spinner is active when the terminal device is determined to be a TTY. This flag disables it regardless.

--oneshot (-1)

Emerge as normal, but do not add the packages to the world file for later updating.

--onlydeps (-o)

Only merge (or pretend to merge) the dependencies of the packages specified, not the packages themselves.

--package-moves[=n]

Perform package moves when necessary. This option is enabled by default. WARNING: This option should remain enabled under normal circumstances. Do not disable it unless you know what you are doing.

--pretend (-p)

Instead of actually performing the merge, simply display what *would* have been installed if --pretend weren't used. Using --pretend is strongly recommended before installing an unfamiliar package. In the printout:

N	new (not yet installed)
S	new SLOT installation (side-by-side versions)
U	updating (to another version)
D	downgrading (best version seems lower)
R	replacing (remerging same version))
F	fetch restricted (must be manually downloaded)
f	fetch restricted (already downloaded)
I	interactive (requires user input)
B	blocked by another package (unresolved conflict)
b	blocked by another package (automatically resolved conflict)

--quiet (-q)

Results may vary, but the general outcome is a reduced or condensed output from portage's displays.

--quiet-build

Redirect all build output to logs alone, and do not display it on stdout.

--quiet-unmerge-warn

Disable the warning message that's shown prior to --unmerge actions. This option is intended to be set in the make.conf(5) EMERGE_DEFAULT_OPTS variable.

--rebuilt-binaries[=n]

Replace installed packages with binary packages that have been rebuilt. Rebuilds are detected by comparison of BUILD_TIME package metadata. This option is enabled automatically when using binary packages (--usepkgonly or --getbinpkgonly) together with --update and --deep.

--rebuilt-binaries-timestamp=TIMESTAMP

This option modifies emerge's behaviour only if --rebuilt-binaries is given. Only binaries that have a BUILD_TIME that is larger than the given TIMESTAMP and that is larger than that of the installed package will be considered by the rebuilt-binaries logic.

--reinstall changed-use

Tells emerge to include installed packages where USE flags have changed since installation. Unlike --newuse, this option does not trigger reinstallation when flags that the user has not enabled are added or removed.

--root=DIR

Set the ROOT environment variable.

--root-deps[=rdeps]

If no argument is given then build-time dependencies of packages for ROOT are installed to ROOT instead of /. If the rdeps argument is given then discard all build-time dependencies of packages for ROOT. This option is only meaningful when used together with ROOT and it should not be enabled under normal circumstances. For currently supported EAPI values, the build-time dependencies are specified in the DEPEND variable. However, behavior may change for new EAPIs when related extensions are added in the future.

--select[=n]

Add specified packages to the world set (inverse of --oneshot). This is useful if you want to use EMERGE_DEFAULT_OPTS to make --oneshot behavior default.

--selective[=n]

This is similar to the --noreplace option, except that it does not take precedence over options such as --newuse. Some options, such as --update, imply --selective. Use --selective=n if you want to forcefully disable --selective, regardless of options like --update.

--skipfirst

This option is only valid when used with --resume. It removes the first package in the resume list. Dependencies are recalculated for remaining packages and any that have unsatisfied dependencies or are masked will be automatically dropped. Also see the related --keep-going option.

--tree (-t)

Shows the dependency tree for the given target by indenting dependencies. This is only really useful in combination with --emptytree or --update and --deep.

--unordered-display

By default the displayed merge list is sorted using the order in which the packages will be merged. When --tree is used together with this option, this constraint is removed, hopefully leading to a more readable dependency tree.

--update (-u)

Updates packages to the best version available, which may not always be the highest version number due to masking for testing and development. Package atoms specified on the command line are greedy, meaning that unspecific atoms may match multiple versions of slotted packages.

--use-ebuild-visibility[=n]

Use unbuilt ebuild metadata for visibility checks on built packages.

--usepkg[=n] (-k)

Tells emerge to use binary packages (from $PKGDIR) if they are available, thus possibly avoiding some time-consuming compiles. This option is useful for CD installs; you can export PKGDIR=/mnt/cdrom/packages and then use this option to have emerge "pull" binary packages from the CD in order to satisfy dependencies.

--usepkgonly[=n] (-K)

Tells emerge to only use binary packages (from $PKGDIR). All the binary packages must be available at the time of dependency calculation or emerge will simply abort. Portage does not use $PORTDIR when calculating dependency information so all masking information is ignored.

--verbose (-v)

Tell emerge to run in verbose mode. Currently this flag causes emerge to print out GNU info errors, if any, and to show the USE flags that will be used for each package when pretending. The following symbols are affixed to USE flags in order to indicate their status:

Symbol	Location	Meaning
-	prefix	not enabled (either disabled or removed)
*	suffix	transition to or from the enabled state
%	suffix	newly added or removed
()	circumfix	forced, masked, or removed

--with-bdeps < y | n >

In dependency calculations, pull in build time dependencies that are not strictly required. This defaults to 'n' for installation actions, meaning they will not be installed, and 'y' for the --depclean action, meaning they will not be removed. This setting can be added to EMERGE_DEFAULT_OPTS (see make.conf(5)) and later overridden via the command line.

ENVIRONMENT OPTIONS

ROOT = [path]

Use ROOT to specify the target root filesystem to be used for merging packages or ebuilds. This variable can be set via the --root option or in make.conf(5) (the command line overrides other settings).
Defaults to /.

PORTAGE_CONFIGROOT = [path]

Use PORTAGE_CONFIGROOT to specify the location for various portage configuration files (see FILES for a detailed list of configuration files). This variable can be set via the --config-root option.
Defaults to /.

OUTPUT

[blocks B ] app-text/dos2unix (app-text/dos2unix is blocking app-text/hd2u-0.8.0)

Dos2unix is Blocking hd2u from being emerged. Blockers are defined when two packages will clobber each others files, or otherwise cause some form of breakage in your system. However, blockers usually do not need to be simultaneously emerged because they usually provide the same functionality.

[ebuild N ] app-games/qstat-25c

Qstat is New to your system, and will be emerged for the first time.

[ebuild NS ] dev-libs/glib-2.4.7

You already have a version of glib installed, but a 'new' version in a different SLOT is available.

[ebuild R ] sys-apps/sed-4.0.5

Sed 4.0.5 has already been emerged, but if you run the command, then portage will Re-emerge the specified package (sed in this case).

[ebuild F ] media-video/realplayer-8-r6

The realplayer package requires that you Fetch the sources manually. When you attempt to emerge the package, if the sources are not found, then portage will halt and you will be provided with instructions on how to download the required files.

[ebuild f ] media-video/realplayer-8-r6

The realplayer package's files are already downloaded.

[ebuild U ] net-fs/samba-2.2.8_pre1 [2.2.7a]

Samba 2.2.7a has already been emerged and can be Updated to version 2.2.8_pre1.

[ebuild UD] media-libs/libgd-1.8.4 [2.0.11]

Libgd 2.0.11 is already emerged, but if you run the command, then portage will Downgrade to version 1.8.4 for you.
This may occur if a newer version of a package has been masked because it is broken or it creates a security risk on your system and a fix has not been released yet.
Another reason this may occur is if a package you are trying to emerge requires an older version of a package in order to emerge successfully. In this case, libgd 2.x is incompatible with libgd 1.x. This means that packages that were created with libgd 1.x will not compile with 2.x and must downgrade libgd first before they can emerge.

[ebuild U ] sys-devel/distcc-2.16 [2.13-r1] USE=ipv6* -gtk -qt%

Here we see that the make.conf variable USE affects how this package is built. In this example, ipv6 optional support is enabled and both gtk and qt support are disabled. The asterisk following ipv6 indicates that ipv6 support was disabled the last time this package was installed. The percent sign following qt indicates that the qt option has been added to the package since it was last installed. For information about all USE symbols, see the --verbose option documentation above.
*Note: Flags that haven't changed since the last install are only displayed when you use the --pretend and --verbose options. Using the --quiet option will prevent all information from being displayed.

NOTES

You also want to typically use --update, which ignores packages that are already fully updated but updates those that are not.

When you install a package with uninstalled dependencies and do not explicitly state those dependencies in the list of parameters, they will not be added to the world file. If you want them to be detected for world updates, make sure to explicitly list them as parameters to emerge.

USE variables may be specified on the command line to override those specified in the default locations, letting you avoid using some dependencies you may not want to have. USE flags specified on the command line are NOT remembered. For example, env USE="-X -gnome" emerge mc will emerge mc with those USE settings (on Bourne-compatible shells you may omit the env part). If you want those USE settings to be more permanent, you can put them in /etc/portage/package.use instead.

If emerge --update system or emerge --update world fails with an error message, it may be that an ebuild uses some newer feature not present in this version of emerge. You can use emerge --update portage to upgrade to the lastest version, which should support any necessary new features.  

MASKED PACKAGES

Masks in portage have many uses: they allow a testing period where the packages can be used in live machines; they prevent the use of a package when it will fail; and they mask existing packages that are broken or could pose a security risk. Read below to find out how to unmask in various cases. Also note that if you give emerge an ebuild, then all forms of masking will be ignored and emerge will attempt to emerge the package.

backtracking

When packages are masked for backtracking, it means that the dependency resolver has temporarily masked them in order to avoid dependency conflicts and/or unsatisfied dependencies. This type of mask is typically accompanied by a message about a missed package update which has been skipped in order to avoid dependency conflicts and/or unsatisfied dependencies.

package.mask

The package.mask file primarily blocks the use of packages that cause problems or are known to have issues on different systems. It resides in /usr/portage/profiles.

CHOST

Use the ACCEPT_CHOSTS variable in make.conf(5) to control CHOST acceptance.

EAPI

The EAPI variable in an ebuild(5) file is used to mask packages that are not supported by the current version of portage. Packages masked by EAPI can only be installed after portage has been upgraded.

KEYWORDS

The KEYWORDS variable in an ebuild file is also used for masking a package still in testing. There are architecture-specific keywords for each package that let portage know which systems are compatible with the package. Packages which compile on an architecture, but have not been proven to be "stable", are masked with a tilde (~) in front of the architecture name. emerge examines the ACCEPT_KEYWORDS environment variable to allow or disallow the emerging of a package masked by KEYWORDS. To inform emerge that it should build these 'testing' versions of packages, you should update your /etc/portage/package.accept_keywords file to list the packages you want the 'testing' version. See portage(5) for more information.

LICENSE

The LICENSE variable in an ebuild file can be used to mask packages based on licensing restrictions. emerge examines the ACCEPT_LICENSE environment variable to allow or disallow the emerging of a package masked by LICENSE. See make.conf(5) for information about ACCEPT_LICENSE, and see portage(5) for information about /etc/portage/package.license.

PROPERTIES

The PROPERTIES variable in an ebuild file can be used to mask packages based on properties restrictions. emerge examines the ACCEPT_PROPERTIES environment variable to allow or disallow the emerging of a package masked by PROPERTIES. See make.conf(5) for information about ACCEPT_PROPERTIES, and see portage(5) for information about /etc/portage/package.properties. Use the --accept-properties option to temporarily override ACCEPT_PROPERTIES.

CONFIGURATION FILES

When Portage installs a file into a protected directory tree like /etc, any existing files will not be overwritten. If a file of the same name already exists, Portage will change the name of the to-be-installed file from 'foo' to '._cfg0000_foo'. If '._cfg0000_foo' already exists, this name becomes '._cfg0001_foo', etc. In this way, existing files are not overwritten, allowing the administrator to manually merge the new config files and avoid any unexpected changes.

In addition to protecting overwritten files, Portage will not delete any files from a protected directory when a package is unmerged. While this may be a little bit untidy, it does prevent potentially valuable config files from being deleted, which is of paramount importance.

Protected directories are set using the CONFIG_PROTECT variable, normally defined in make.globals. Directory exceptions to the CONFIG_PROTECTed directories can be specified using the CONFIG_PROTECT_MASK variable. To find files that need to be updated in /etc, type find /etc -iname '._cfg????_*'.

You can disable this feature by setting CONFIG_PROTECT="-*" in /etc/make.conf. Then, Portage will mercilessly auto-update your config files. Alternatively, you can leave Config File Protection on but tell Portage that it can overwrite files in certain specific /etc subdirectories. For example, if you wanted Portage to automatically update your rc scripts and your wget configuration, but didn't want any other changes made without your explicit approval, you'd add this to /etc/make.conf:

CONFIG_PROTECT_MASK=/etc/wget /etc/rc.d

Tools such as dispatch-conf, cfg-update, and etc-update are also available to aid in the merging of these files. They provide interactive merging and can auto-merge trivial changes.  

REPORTING BUGS

http://bugs.gentoo.org/

Please include the output of emerge --info when you submit your bug report.  

AUTHORS

Daniel Robbins <drobbins@gentoo.org>
Geert Bevin <gbevin@gentoo.org>
Achim Gottinger <achim@gentoo.org>
Nicholas Jones <carpaski@gentoo.org>
Phil Bordelon <phil@thenexusproject.org>
Mike Frysinger <vapier@gentoo.org>
Marius Mauch <genone@gentoo.org>
Jason Stubbs <jstubbs@gentoo.org>
Brian Harring <ferringb@gmail.com>
Zac Medico <zmedico@gentoo.org>

FILES

/var/lib/portage/world

Contains a list of all user-specified packages. You can safely edit this file, adding packages that you want to be considered in world set updates and removing those that you do not want to be considered.

/etc/make.conf

Contains variables for the build process, overriding those in make.globals.

/etc/portage/color.map

Contains variables customizing colors.

/etc/dispatch-conf.conf

Contains settings to handle automatic updates/backups of configuration files.

/etc/make.profile/make.defaults

Contains profile-specific variables for the build process. Do not edit this file.

/usr/portage/profiles/use.desc

Contains the master list of USE flags with descriptions of their functions. Do not edit this file.

/etc/make.profile/virtuals

Contains a list of default packages used to resolve virtual dependencies. Do not edit this file.

/etc/make.profile/packages

Contains a list of packages used for the base system. The system and world sets consult this file. Do not edit this file.

/usr/share/portage/config/make.globals

Contains the default variables for the build process. Do not edit this file.

SEE ALSO

A number of helper applications reside in /usr/lib/portage/bin.

The app-portage/gentoolkit package contains useful scripts such as equery (a package query tool).

Index

NAME

SYNOPSIS

DESCRIPTION

EBUILDS, TBZ2S, SETS AND ATOMS

ACTIONS

OPTIONS

ENVIRONMENT OPTIONS

OUTPUT

NOTES

MASKED PACKAGES

CONFIGURATION FILES

REPORTING BUGS

AUTHORS

FILES

SEE ALSO