1 .TH "EMERGE" "1" "Sep 2012" "Portage VERSION" "Portage"
3 emerge \- Command\-line interface to the Portage system
7 [\fIoptions\fR] [\fIaction\fR] [\fIebuild\fR | \fItbz2file\fR | \fIfile\fR | \fI@set\fR | \fIatom\fR] ...
10 \fB\-\-sync\fR | \fB\-\-version\fR
13 \fB\-\-info\fR [\fIatom\fR]
16 \fB\-\-search\fR \fIsomestring\fR
19 \fB\-\-help\fR [\fB\-\-verbose\fR]
21 \fBemerge\fR is the definitive command\-line interface to the Portage
22 system. It is primarily used for installing packages, and \fBemerge\fR
23 can automatically handle any dependencies that the desired package has.
24 \fBemerge\fR can also update the \fBportage tree\fR, making new and
25 updated packages available. \fBemerge\fR gracefully handles updating
26 installed packages to newer releases as well. It handles both source
27 and binary packages, and it can be used to create binary packages for
29 .SH "EBUILDS, TBZ2S, SETS AND ATOMS"
30 \fBemerge\fR primarily installs packages. You can specify
31 packages to install in five possible ways: an \fIatom\fR,
32 a \fIset\fR, an installed \fIfile\fR, an \fIebuild\fR, or
37 An \fIebuild\fR must be, at a minimum, a valid Portage
38 package directory name without a version or category, such as
39 \fBportage\fR or \fBpython\fR.
40 Both categories and version numbers may be used in addition, such
41 as \fBsys\-apps/portage\fR or \fB=python\-2.2.1\-r2\fR.
43 ignores a trailing slash so that filename completion can be used.
44 The \fIebuild\fR may also be an actual filename, such as
45 \fB/usr/portage/app\-admin/python/python\-2.2.1\-r2.ebuild\fR.
46 \fBWARNING:\fR The implementation of \fBemerge /path/to/ebuild\fR is broken and
47 so this syntax shouldn't be used.
50 A \fItbz2file\fR must be a valid .tbz2 created with \fBebuild
51 <package>\-<version>.ebuild package\fR or \fBemerge \-\-buildpkg
52 [category/]<package>\fR or \fBquickpkg /var/db/pkg/<category>/<package>\fR.
55 A \fIfile\fR must be a file or directory that has been installed by one or
56 more packages. If an absolute path is not used, then it must begin with
57 either "./" or "../". For directories that are owned by multiple packages, all
58 owning packages will be selected. See the portageq(1) owners command if you
59 would like to query the owners of one or more files or directories.
62 A \fIset\fR is a convenient shorthand for a large group of
63 packages. Three sets are currently always available: \fBselected\fR,
64 \fBsystem\fR and \fBworld\fR. \fBselected\fR contains the user-selected
65 "world" packages that are listed in \fB/var/lib/portage/world\fR,
66 and nested sets that may be listed
67 in \fB/var/lib/portage/world_sets\fR. \fBsystem\fR refers to a set of
68 packages deemed necessary for your system to run properly. \fBworld\fR
69 encompasses both the \fBselected\fR and \fBsystem\fR sets. [See
70 \fBFILES\fR below for more information.] Other sets can exist depending
71 on the current configuration. The default set configuration is located
72 in the \fB/usr/share/portage/config/sets\fR directory.
73 User sets may be created by placing files in the \fB/etc/portage/sets/\fR
74 directory (see \fBportage\fR(5)). Note that a \fIset\fR
75 is generally used in conjunction with \fB\-\-update\fR. When used as
76 arguments to \fBemerge\fR sets have to be prefixed with \fB@\fR to be
77 recognized. Use the \fB\-\-list\-sets\fR action to display a list of
78 available package sets.
81 An \fIatom\fR describes bounds on a package that you wish to install.
82 \fISee ebuild(5) for the details on atom syntax.\fR For example,
83 \fB>=dev\-lang/python\-2.2.1\-r2\fR matches the latest available version of
84 Python greater than or equal to 2.2.1\-r2. Similarly,
85 \fB<dev\-lang/python\-2.0\fR matches the latest available version of Python
86 before 2.0. Note that in many shells you will need to escape characters such
87 as '<' and '='; use single\- or double\-quotes around the \fIatom\fR
88 to get around escaping problems.
92 If no action is specified, the action is to merge in the specified
93 packages, satisfying any dependencies that they may have. The
94 arguments can be \fIatoms\fR, \fIsets\fR, installed \fIfiles\fR,
95 \fIebuilds\fR, or \fItbz2s\fR.
96 \fBNote that you need to use the \-\-usepkg
97 option if you want to install a tbz2\fR. The packages are added
98 to the \fBworld\fR file at the end, so that they are considered for
102 Scan all repositories for relevant unread GLEP 42 news items, and display
103 how many are found. See \fIhttp://www.gentoo.org/proj/en/glep/glep-0042.html\fR.
106 Cleans up the system by examining the installed packages and removing older
107 packages. This is accomplished by looking at each installed package and separating
108 the installed versions by \fBslot\fR. Clean will \fBremove all but the most recently
109 installed version in each \fbslot\fR. Clean should not remove unslotted packages.
110 Note: Most recently installed means most \fBrecent\fR, not highest version.
113 Run package specific actions needed to be executed after the emerge process
114 has completed. This usually entails configuration file setup or other similar
115 setups that the user may wish to run.
117 .BR "\-\-depclean (-c)"
118 Cleans the system by removing packages that are not associated
119 with explicitly merged packages. Depclean works by creating the
120 full dependency tree from the @world set,
121 then comparing it to installed packages. Packages installed, but
122 not part of the dependency tree, will be uninstalled by depclean.
123 See \fB\-\-with\-bdeps\fR for behavior with respect to build time dependencies
124 that are not strictly required. Packages that are part of the world set will
125 always be kept. They can be manually added to this set with \fIemerge
126 \-\-noreplace <atom>\fR. As a safety measure, depclean will not remove any
127 packages unless *all* required dependencies have been resolved. As a
128 consequence, it is often necessary to run \fIemerge \-\-update \-\-newuse
129 \-\-deep @world\fR prior to depclean. Also note that
130 depclean may break link level dependencies, especially when the
131 \fB\-\-depclean\-lib\-check\fR option is disabled. Thus, it is
132 recommended to use a tool such as \fBrevdep-rebuild\fR(1)
133 in order to detect such breakage.
136 Inexperienced users are advised to use \fB\-\-pretend\fR or \fB\-\-ask\fR
137 with this option in order to see a preview of which packages
138 will be uninstalled. Always study the list of packages
139 to be cleaned for any obvious mistakes. Note that packages listed in
140 package.provided (see \fBportage\fR(5)) may be removed by
141 depclean, even if they are part of the world set.
143 Depclean serves as a dependency aware
144 version of \fB\-\-unmerge\fR. When given one or more atoms, it will
145 unmerge matched packages that have no reverse dependencies. Use
146 \fB\-\-depclean\fR together with \fB\-\-verbose\fR to show reverse
149 .BR "\-\-deselect [ y | n ]"
150 Remove atoms and/or sets from the world file. This action is implied
151 by uninstall actions, including \fB-\-depclean\fR,
152 \fB-\-prune\fR and \fB-\-unmerge\fR. Use \fB-\-deselect=n\fR
153 in order to prevent uninstall actions from removing
154 atoms from the world file.
156 .BR "\-\-help " (\fB\-h\fR)
157 Displays help information for emerge. Adding one of the additional
158 arguments listed above will give you more specific help information
159 on that subject. The internal \fBemerge\fR help documentation is
160 updated more frequently than this man page; check it out if you
161 are having problems that this man page does not help resolve.
164 Produces a list of information to include in bug reports which aids the
165 developers when fixing the reported problem. \fBPlease include this
166 information when submitting a bug report.\fR Expanded output can be obtained
167 with the \fI\-\-verbose\fR option.
170 Displays a list of available package sets.
173 Transfers metadata cache from ${PORTDIR}/metadata/cache/ to
174 /var/cache/edb/dep/ as is normally done on the
175 tail end of an rsync update using \fBemerge \-\-sync\fR. This process
176 populates the cache database that portage uses for pre-parsed lookups of
177 package data. It does not populate cache for the overlays listed in
178 PORTDIR_OVERLAY. In order to generate cache for overlays, use \fB\-\-regen\fR.
179 In versions of portage >=2.1.5 the \-\-metadata action is totally unnecessary
180 unless the user has enabled FEATURES="metadata-transfer" in \fBmake.conf\fR(5).
182 .BR "\-\-prune " (\fB\-P\fR)
183 Removes all but the highest installed version of a package from your
184 system. Use \fB\-\-prune\fR together with \fB\-\-verbose\fR to show
185 reverse dependencies or with \fB\-\-nodeps\fR to ignore all dependencies.
186 \fBWARNING: This action can remove packages from your world file! Check
187 the emerge output of the next \-\-depclean run carefully! Use
188 \-\-depclean to avoid this issue.\fR
191 Causes portage to check and update the dependency cache of all ebuilds in the
192 portage tree. The cache is used to speed up searches and the building of
193 dependency trees. This command is not recommended for rsync users as rsync
194 updates the cache using server\-side caches. If you do not know the
195 differences between a 'rsync user' and some other user, then you are a 'rsync
196 user' :). Rsync users should simply run \fBemerge \-\-sync\fR to regenerate
197 the cache. After a portage update, rsync users may find it convenient to run
198 \fBemerge \-\-metadata\fR to rebuild the cache as portage does at the end of
199 a sync operation. In order to specify parallel \fB\-\-regen\fR behavior, use
200 the \fB\-\-jobs\fR and \fB\-\-load\-average\fR options. If you would like to
201 generate and distribute cache for use by others, use \fBegencache\fR(1).
203 .BR "\-\-resume" (\fB\-r\fR)
204 Resumes the most recent merge list that has been aborted due to an error.
205 This re\-uses the options that were given with the original
206 command that's being resumed, and the user may also provide
207 additional options when calling \fB\-\-resume\fR.
208 Please note that this operation will only return an error on failure. If there
209 is nothing for portage to do, then portage will exit with a message and a
210 success condition. A resume list will persist until it has been completed in
211 entirety or until another aborted merge list replaces it. The resume history
212 is capable of storing two merge lists. After one resume list completes, it is
213 possible to invoke \-\-resume once again in order to resume an older list.
215 .BR "\-\-search " (\fB\-s\fR)
216 Searches for matches of the supplied string in the portage tree.
217 By default emerge uses a case-insensitive simple search, but you can
218 enable a regular expression search by prefixing the search string with %.
219 For example, \fBemerge \-\-search "%^kde"\fR searches for any package whose
220 name starts with "kde"; \fBemerge \-\-search "%gcc$"\fR searches for any
221 package that ends with "gcc"; \fBemerge \-\-search "office"\fR searches for
222 any package that contains the word "office". If you want to include the
223 category into the search string, prepend an @: \fBemerge \-\-search
224 "%@^dev-java.*jdk"\fR. If you want to search the package descriptions as well,
225 use the \fB\-\-searchdesc\fR action.
227 .BR "\-\-searchdesc " (\fB\-S\fR)
228 Matches the search string against the description field as well as
229 the package name. \fBTake caution\fR as the descriptions are also
230 matched as regular expressions.
233 This updates the portage tree that is located in the
234 directory that the PORTDIR variable refers to (default
235 location is /usr/portage). The SYNC variable specifies
236 the remote URI from which files will be synchronized.
237 The \fBPORTAGE_SYNC_STALE\fR variable configures
238 warnings that are shown when emerge \-\-sync has not
239 been executed recently.
242 The emerge \-\-sync action will modify and/or delete
243 files located inside the directory that the PORTDIR
244 variable refers to (default location is /usr/portage).
245 For more information, see the PORTDIR documentation in
246 the make.conf(5) man page.
249 The \fBemerge\-webrsync\fR program will download the entire
250 portage tree as a tarball, which is much faster than emerge
251 \-\-sync for first time syncs.
254 .BR "\-\-unmerge " (\fB\-C\fR)
255 \fBWARNING: This action can remove important packages!\fR Removes
256 all matching packages. This does no checking of dependencies, so
257 it may remove packages necessary for the proper operation of your
258 system. Its arguments can be \fIatoms\fR or
259 \fIebuilds\fR. For a dependency aware version of \fB\-\-unmerge\fR,
260 use \fB\-\-depclean\fR or \fB\-\-prune\fR.
262 .BR "\-\-version " (\fB\-V\fR)
263 Displays the version number of \fBemerge\fR.
266 .BR \-\-accept\-properties=ACCEPT_PROPERTIES
267 This option temporarily overrides the \fBACCEPT_PROPERTIES\fR
268 variable. The \fBACCEPT_PROPERTIES\fR variable is incremental,
269 which means that the specified setting is appended to the
270 existing value from your configuration. The special \fB-*\fR
271 token can be used to discard the existing configuration
272 value and start fresh. See the \fBMASKED PACKAGES\fR section
273 and \fBmake.conf\fR(5) for more information about
274 ACCEPT_PROPERTIES. A typical usage example for this option
275 would be to use \fI\-\-accept\-properties=\-interactive\fR to
276 temporarily mask interactive packages. With default
277 configuration, this would result in an effective
278 \fBACCEPT_PROPERTIES\fR value of "* -interactive".
280 .BR "\-\-alphabetical "
281 When displaying USE and other flag output, combines the enabled and
282 disabled lists into one list and sorts the whole list alphabetically.
284 .BR "\-\-ask [ y | n ] (\-a short option)"
285 Before performing the action, display what will take place (server info for
286 \fB\-\-sync\fR, \fB\-\-pretend\fR output for merge, and so forth), then ask
287 whether to proceed with the action or abort. Using \fB\-\-ask\fR is more
288 efficient than using \fB\-\-pretend\fR and then executing the same command
289 without \fB\-\-pretend\fR, as dependencies will only need to be calculated once.
290 \fBWARNING: If the "Enter" key is pressed at the prompt (with no other input),
291 it is interpreted as acceptance of the first choice. Note that the input
292 buffer is not cleared prior to the prompt, so an accidental press of the
293 "Enter" key at any time prior to the prompt will be interpreted as a choice!
294 Use the \-\-ask\-enter\-invalid option if you want a single "Enter" key
295 press to be interpreted as invalid input.\fR
297 .BR "\-\-ask\-enter\-invalid"
298 When used together with the \fB\-\-ask\fR option,
299 interpret a single "Enter" key press as
300 invalid input. This helps prevent accidental
301 acceptance of the first choice. This option is
302 intended to be set in the \fBmake.conf\fR(5)
303 \fBEMERGE_DEFAULT_OPTS\fR variable.
305 .BR "\-\-autounmask [ y | n ]"
306 Automatically unmask packages and generate package.use
307 settings as necessary to satisfy dependencies. This
308 option is enabled by default. If any configuration
309 changes are required, then they will be displayed
310 after the merge list and emerge will immediately
311 abort. If the displayed configuration changes are
312 satisfactory, you should copy and paste them into
313 the specified configuration file(s), or enable the
314 \fB\-\-autounmask\-write\fR option. The
315 \fBEMERGE_DEFAULT_OPTS\fR variable may be used to
316 disable this option by default in \fBmake.conf\fR(5).
318 .BR "\-\-autounmask\-unrestricted\-atoms [ y | n ]"
319 If \-\-autounmask is enabled, keyword and mask changes
320 using the \'=\' operator will be written. With this
321 option, \'>=\' operators will be used whenever possible.
322 USE and license changes always use the latter behavior.
324 .BR "\-\-autounmask\-keep\-masks [ y | n ]"
325 If \-\-autounmask is enabled, no package.unmask or ** keyword changes
326 will be created. This leads to unsatisfied dependencies if
327 no other solution exists.
329 .BR "\-\-autounmask\-write [ y | n ]"
330 If \-\-autounmask is enabled, changes are written
331 to config files, respecting \fBCONFIG_PROTECT\fR and \fB\-\-ask\fR.
332 If the corresponding package.* is a file, the changes are appended to
333 it, if it is a directory, changes are written to the lexicographically
334 last file. This way it is always ensured that the new changes take
335 precedence over existing changes.
337 .BR \-\-backtrack=COUNT
338 Specifies an integer number of times to backtrack if
339 dependency calculation fails due to a conflict or an
340 unsatisfied dependency (default: \'10\').
342 .BR "\-\-binpkg\-respect\-use [ y | n ]"
343 Tells emerge to ignore binary packages if their use flags
344 don't match the current configuration. (default: \'n\')
346 .BR "\-\-buildpkg [ y | n ] (\-b short option)"
347 Tells emerge to build binary packages for all ebuilds processed in
348 addition to actually merging the packages. Useful for maintainers
349 or if you administrate multiple Gentoo Linux systems (build once,
350 emerge tbz2s everywhere) as well as disaster recovery. The package
351 will be created in the \fBPKGDIR\fR directory (see \fBmake.conf\fR(5)).
352 An alternative for already\-merged
353 packages is to use \fBquickpkg\fR(1) which creates a tbz2 from the
356 .BR "\-\-buildpkg\-exclude " ATOMS
357 A space separated list of package atoms for which
358 no binary packages should be built. This option overrides all
359 possible ways to enable building of binary packages.
361 .BR "\-\-buildpkgonly " (\fB\-B\fR)
362 Creates binary packages for all ebuilds processed without actually
363 merging the packages. This comes with the caveat that all build-time
364 dependencies must already be emerged on the system.
366 .BR "\-\-changed\-use"
367 Tells emerge to include installed packages where USE flags have
368 changed since installation. This option also implies the
369 \fB\-\-selective\fR option. Unlike \fB\-\-newuse\fR, the
370 \fB\-\-changed\-use\fR option does not trigger reinstallation when
371 flags that the user has not enabled are added or removed.
373 NOTE: This option ignores the state of the "test" USE flag, since that flag
374 has a special binding to FEATURES="test" (see \fBmake.conf\fR(5) for more
375 information about \fBFEATURES\fR settings).
377 .BR "\-\-changelog " (\fB\-l\fR)
378 Use this in conjunction with the \fB\-\-pretend\fR option. This will
379 show the ChangeLog entries for all the packages that will be upgraded.
381 .BR "\-\-color < y | n >"
382 Enable or disable color output. This option will override \fINOCOLOR\fR
383 (see \fBmake.conf\fR(5)) and may also be used to force color output when stdout
384 is not a tty (by default, color is disabled unless stdout is a tty).
387 Used alongside \fB\-\-pretend\fR to cause the package name, new version,
388 and old version to be displayed in an aligned format for easy cut\-n\-paste.
390 .BR "\-\-complete\-graph [ y | n ]"
391 This causes \fBemerge\fR to consider the deep dependencies of all
392 packages from the world set. With this option enabled,
393 \fBemerge\fR will bail out if it determines that the given operation will
394 break any dependencies of the packages that have been added to the
395 graph. Like the \fB\-\-deep\fR option, the \fB\-\-complete\-graph\fR
396 option will significantly increase the time taken for dependency
397 calculations. Note that, unlike the \fB\-\-deep\fR option, the
398 \fB\-\-complete\-graph\fR option does not cause any more packages to
399 be updated than would have otherwise been updated with the option disabled.
400 Using \fB\-\-with\-bdeps=y\fR together with \fB\-\-complete\-graph\fR makes
401 the graph as complete as possible.
403 .BR "\-\-complete\-graph\-if\-new\-use < y | n >"
404 Trigger the \fB\-\-complete\-graph\fR behavior if USE or IUSE will
405 change for an installed package. This option is enabled by default.
407 .BR "\-\-complete\-graph\-if\-new\-ver < y | n >"
408 Trigger the \fB\-\-complete\-graph\fR behavior if an installed package
409 version will change (upgrade or downgrade). This option is enabled by default.
411 .BR \-\-config\-root=DIR
412 Set the \fBPORTAGE_CONFIGROOT\fR environment variable.
414 .BR "\-\-debug " (\fB\-d\fR)
415 Tells emerge to run the emerge command in \fB\-\-debug\fR mode. In this
416 mode the bash build environment will run with the \-x option, causing
417 it to output verbose debugging information to stdout. This also enables
418 a plethora of other output (mostly dependency resolution messages).
420 .BR "\-\-deep [DEPTH] " (\fB\-D\fR)
422 \fBemerge\fR to consider the entire dependency tree of packages,
423 instead of checking only the immediate dependencies of the packages.
424 As an example, this catches updates in libraries that are not directly
425 listed in the dependencies of a package. Also see \fB\-\-with\-bdeps\fR for
426 behavior with respect to build time dependencies that are not strictly
429 .BR "\-\-depclean\-lib\-check [ y | n ]"
430 Account for library link-level dependencies during
431 \fB\-\-depclean\fR and \fB\-\-prune\fR actions.
432 This option is enabled by default. This option is ignored
433 when FEATURES="preserve\-libs" is enabled in
434 \fBmake.conf\fR(5), since any libraries that have
435 consumers will simply be preserved.
437 .BR "\-\-dynamic\-deps < y | n >"
438 In dependency calculations, substitute the dependencies of installed
439 packages with the dependencies of corresponding unbuilt ebuilds from
440 source repositories. This causes the effective dependencies of
441 installed packages to vary dynamically when source ebuild dependencies
442 are modified. This option is enabled by default.
445 If you want to disable \-\-dynamic\-deps, then it may be necessary to
446 first run \fBfixpackages\fR(1) in order to get the best results. The
447 \fBfixpackages\fR(1) command performs two different operations that can
448 also be performed separately by the `emaint \-\-fix moveinst` and
449 `emaint \-\-fix movebin` commands (see \fBemaint\fR(1)).
451 .BR "\-\-emptytree " (\fB\-e\fR)
452 Reinstalls target atoms and their entire deep
453 dependency tree, as though no packages are currently
454 installed. You should run this with \fB\-\-pretend\fR
455 first to make sure the result is what you expect.
457 .BR "\-\-exclude " ATOMS
458 A space separated list of package names or slot atoms.
459 Emerge won't install any ebuild or binary package that
460 matches any of the given package atoms.
462 .BR "\-\-fail\-clean [ y | n ]"
463 Clean up temporary files after a build failure. This is
464 particularly useful if you have \fBPORTAGE_TMPDIR\fR on
465 tmpfs. If this option is enabled, you probably also want
466 to enable \fBPORT_LOGDIR\fR (see \fBmake.conf\fR(5)) in
467 order to save the build log.
469 .BR "\-\-fetchonly " (\fB\-f\fR)
470 Instead of doing any package building, just perform fetches for all
471 packages (fetch things from SRC_URI based upon USE setting).
473 .BR "\-\-fetch\-all\-uri " (\fB\-F\fR)
474 Instead of doing any package building, just perform fetches for all
475 packages (fetch everything in SRC_URI regardless of USE setting).
477 .BR "\-\-getbinpkg [ y | n ] (\-g short option)"
478 Using the server and location defined in \fIPORTAGE_BINHOST\fR (see
479 \fBmake.conf\fR(5)), portage will download the information from each binary
480 package found and it will use that information to help build the dependency
481 list. This option implies \fB\-k\fR. (Use \fB\-gK\fR for binary\-only
484 .BR "\-\-getbinpkgonly [ y | n ] (\-G short option)"
485 This option is identical to \fB\-g\fR, as above, except binaries from the
486 remote server are preferred over local packages if they are not identical.
488 .BR "\-\-ignore-default-opts"
489 Causes \fIEMERGE_DEFAULT_OPTS\fR (see \fBmake.conf\fR(5)) to be ignored.
491 .BR "\-\-ignore\-built\-slot\-operator\-deps < y | n >"
492 Ignore the slot/sub\-slot := operator parts of dependencies that have
493 been recorded when packages where built. This option is intended
494 only for debugging purposes, and it only affects built packages
495 that specify slot/sub\-slot := operator dependencies which are
496 supported beginning with \fBEAPI 5\fR.
498 .BR "-j [JOBS], \-\-jobs[=JOBS]"
499 Specifies the number of packages to build simultaneously. If this option is
500 given without an argument, emerge will not limit the number of jobs that can
501 run simultaneously. Also see the related \fB\-\-load\-average\fR option.
502 Similarly to the \-\-quiet\-build option, the \-\-jobs option causes all
503 build output to be redirected to logs.
504 Note that interactive packages currently force a setting
505 of \fI\-\-jobs=1\fR. This issue can be temporarily avoided
506 by specifying \fI\-\-accept\-properties=\-interactive\fR.
508 .BR "\-\-keep\-going [ y | n ]"
509 Continue as much as possible after an error. When an error occurs,
510 dependencies are recalculated for remaining packages and any with
511 unsatisfied dependencies are automatically dropped. Also see
512 the related \fB\-\-skipfirst\fR option.
514 .BR \-\-load\-average=LOAD
515 Specifies that no new builds should be started if there are other builds
516 running and the load average is at least LOAD (a floating-point number).
517 This option is recommended for use in combination with \fB\-\-jobs\fR in
518 order to avoid excess load. See \fBmake\fR(1) for information about
519 analogous options that should be configured via \fBMAKEOPTS\fR in
522 .BR "\-\-misspell\-suggestions < y | n >"
523 Enable or disable misspell suggestions. By default, emerge will show
524 a list of packages with similar names when a package doesn't exist.
525 The \fIEMERGE_DEFAULT_OPTS\fR variable may be used to disable this
528 .BR "\-\-newuse " (\fB\-N\fR)
529 Tells emerge to include installed packages where USE
530 flags have changed since compilation. This option
531 also implies the \fB\-\-selective\fR option.
532 USE flag changes include:
534 A USE flag was added to a package.
535 A USE flag was removed from a package.
536 A USE flag was turned on for a package.
537 A USE flag was turned off for a package.
539 USE flags may be toggled by your profile as well as your USE and package.use
540 settings. If you would like to skip rebuilds for which disabled flags have
541 been added to or removed from IUSE, see the related
542 \fB\-\-changed\-use\fR option. If you would like to skip rebuilds for
543 specific packages, see the \fB\-\-exclude\fR option.
545 NOTE: This option ignores the state of the "test" USE flag, since that flag
546 has a special binding to FEATURES="test" (see \fBmake.conf\fR(5) for more
547 information about \fBFEATURES\fR settings).
550 Causes portage to disregard merge records indicating that a config file
551 inside of a \fBCONFIG_PROTECT\fR directory has been merged already. Portage
552 will normally merge those files only once to prevent the user from
553 dealing with the same config multiple times. This flag will cause the
554 file to always be merged.
556 .BR "\-\-nodeps " (\fB\-O\fR)
557 Merges specified packages without merging any dependencies. Note that
558 the build may fail if the dependencies aren't satisfied.
560 .BR "\-\-noreplace " (\fB\-n\fR)
561 Skips the packages specified on the command\-line that have already
562 been installed. Without this option, any package atoms or package sets
563 you specify on the command\-line \fBwill\fR cause Portage to remerge
564 the package, even if it is already installed. Note that Portage will
565 not remerge dependencies by default.
568 Disables the spinner for the session. The spinner is active when the
569 terminal device is determined to be a TTY. This flag disables it regardless.
571 .BR "\-\-usepkg\-exclude " ATOMS
572 A space separated list of package names or slot atoms. Emerge will ignore
573 matching binary packages.
575 .BR "\-\-rebuild\-exclude " ATOMS
576 A space separated list of package names or slot atoms. Emerge will not rebuild
577 matching packages due to \fB\-\-rebuild\fR.
579 .BR "\-\-rebuild\-ignore " ATOMS
580 A space separated list of package names or slot atoms. Emerge will not rebuild
581 packages that depend on matching packages due to \fB\-\-rebuild\fR.
583 .BR "\-\-oneshot " (\fB\-1\fR)
584 Emerge as normal, but do not add the packages to the world file
587 .BR "\-\-onlydeps " (\fB\-o\fR)
588 Only merge (or pretend to merge) the dependencies of the packages
589 specified, not the packages themselves.
591 .BR "\-\-package\-moves [ y | n ]"
592 Perform package moves when necessary. This option is enabled
593 by default. Package moves are typically applied immediately
594 after a \fB\-\-sync\fR action. They are applied in an
595 incremental fashion, using only the subset of the history of
596 package moves which have been added or modified since the
597 previous application of package moves.
599 \fBWARNING:\fR This option
600 should remain enabled under normal circumstances.
601 Do not disable it unless you know what you are
604 \fBNOTE:\fR The \fBfixpackages\fR(1) command can be used to
605 exhaustively apply the entire history of package moves,
606 regardless of whether or not any of the package moves have
607 been previously applied.
609 .BR "\-\-pretend " (\fB\-p\fR)
610 Instead of actually performing the merge, simply display what *would*
611 have been installed if \fB\-\-pretend\fR weren't used. Using \fB\-\-pretend\fR
612 is strongly recommended before installing an unfamiliar package. In
617 N new (not yet installed)
618 S new SLOT installation (side-by-side versions)
619 U updating (to another version)
620 D downgrading (best version seems lower)
621 r reinstall (forced due to slot or sub\-slot change of a dependency)
622 R replacing (remerging same version)
623 F fetch restricted (must be manually downloaded)
624 f fetch restricted (already downloaded)
625 I interactive (requires user input)
626 B blocked by another package (unresolved conflict)
627 b blocked by another package (automatically resolved conflict)
630 .BR "\-\-quiet [ y | n ] (\-q short option)"
631 Results may vary, but the general outcome is a reduced or condensed
632 output from portage's displays.
634 .BR "\-\-quiet\-build [ y | n ]"
635 Redirect all build output to logs alone, and do not display it on
636 stdout. If a build failure occurs for a single package, the build
637 log will be automatically displayed on stdout. If there are multiple
638 build failures (due to options like \-\-keep\-going or \-\-jobs),
639 then the content of the log files will not be displayed, and instead
640 the paths of the log files will be displayed together with the
641 corresponding die messages.
642 Note that interactive packages currently force all build output to
643 be displayed on stdout. This issue can be temporarily avoided
644 by specifying \fI\-\-accept\-properties=\-interactive\fR.
646 .BR "\-\-quiet\-repo\-display"
647 In the package merge list display, suppress ::repository output, and
648 instead use numbers to indicate which repositories package come from.
650 .BR \-\-quiet\-unmerge\-warn
651 Disable the warning message that's shown prior to
652 \fB\-\-unmerge\fR actions. This option is intended
653 to be set in the \fBmake.conf\fR(5)
654 \fBEMERGE_DEFAULT_OPTS\fR variable.
656 .BR "\-\-rebuild\-if\-new\-slot [ y | n ]"
657 Automatically rebuild or reinstall packages when slot/sub\-slot :=
658 operator dependencies can be satisfied by a newer slot, so that
659 older packages slots will become eligible for removal by the
660 \-\-depclean action as soon as possible. This option only
661 affects packages that specify slot/sub\-slot := dependencies
662 which are supported beginning with \fBEAPI 5\fR.
663 Since this option requires
664 checking of reverse dependencies, it enables \-\-complete\-graph
665 mode whenever a new slot is installed. This option is enabled by
668 .BR "\-\-rebuild\-if\-new\-rev [ y | n ]"
669 Rebuild packages when build\-time dependencies are built from source, if the
670 dependency is not already installed with the same version and revision.
672 .BR "\-\-rebuild\-if\-new\-ver [ y | n ]"
673 Rebuild packages when build\-time dependencies are built from source, if the
674 dependency is not already installed with the same version. Revision numbers
677 .BR "\-\-rebuild\-if\-unbuilt [ y | n ]"
678 Rebuild packages when build\-time dependencies are built from source.
680 .BR "\-\-rebuilt\-binaries [ y | n ]"
681 Replace installed packages with binary packages that have
682 been rebuilt. Rebuilds are detected by comparison of
683 BUILD_TIME package metadata. This option is enabled
684 automatically when using binary packages
685 (\fB\-\-usepkgonly\fR or \fB\-\-getbinpkgonly\fR) together with
686 \fB\-\-update\fR and \fB\-\-deep\fR.
688 .BR "\-\-rebuilt\-binaries\-timestamp=TIMESTAMP"
689 This option modifies emerge's behaviour only if
690 \fB\-\-rebuilt\-binaries\fR is given. Only binaries that
691 have a BUILD_TIME that is larger than the given TIMESTAMP
692 and that is larger than that of the installed package will
693 be considered by the rebuilt\-binaries logic.
695 .BR "\-\-reinstall changed\-use"
696 This is an alias for \fB\-\-changed\-use\fR.
698 .BR "\-\-reinstall\-atoms " ATOMS
699 A space separated list of package names or slot atoms. Emerge will treat
700 matching packages as if they are not installed, and reinstall them if
704 Set the \fBROOT\fR environment variable.
706 .BR "\-\-root\-deps[=rdeps]"
707 If no argument is given then build\-time dependencies of packages for
708 \fBROOT\fR are installed to \fBROOT\fR instead of /.
709 If the \fBrdeps\fR argument is given then discard all build\-time dependencies
710 of packages for \fBROOT\fR.
711 This option is only meaningful when used together with \fBROOT\fR and it should
712 not be enabled under normal circumstances!
714 Does not affect EAPIs that support \fBHDEPEND\fR.
715 Experimental \fBEAPI 5-hdepend\fR provides \fBHDEPEND\fR as a new
716 means to adjust installation into "\fI/\fR" and \fBROOT\fR.
717 If ebuilds using EAPIs which \fIdo not\fR support \fBHDEPEND\fR are built in
718 the same \fBemerge\fR run as those using EAPIs which \fIdo\fR support
719 \fBHDEPEND\fR, this option affects only the former.
721 .BR "\-\-select [ y | n ]"
722 Add specified packages to the world set (inverse of
723 \fB\-\-oneshot\fR). This is useful if you want to
724 use \fBEMERGE_DEFAULT_OPTS\fR to make
725 \fB\-\-oneshot\fR behavior default.
727 .BR "\-\-selective [ y | n ]"
728 This is identical to the \fB\-\-noreplace\fR option.
729 Some options, such as \fB\-\-update\fR, imply \fB\-\-selective\fR.
730 Use \fB\-\-selective=n\fR if you want to forcefully disable
731 \fB\-\-selective\fR, regardless of options like \fB\-\-changed\-use\fR,
732 \fB\-\-newuse\fR, \fB\-\-noreplace\fR, or \fB\-\-update\fR.
735 This option is only valid when used with \fB\-\-resume\fR. It removes the
736 first package in the resume list. Dependencies are recalculated for
737 remaining packages and any that have unsatisfied dependencies or are
738 masked will be automatically dropped. Also see the related
739 \fB\-\-keep\-going\fR option.
741 .BR "\-\-tree " (\fB\-t\fR)
742 Shows the dependency tree for the given target by indenting dependencies.
743 This is only really useful in combination with \fB\-\-emptytree\fR or
744 \fB\-\-update\fR and \fB\-\-deep\fR.
746 .BR "\-\-unordered\-display"
747 By default the displayed merge list is sorted using the
748 order in which the packages will be merged. When
749 \fB\-\-tree\fR is used together with this option, this
750 constraint is removed, hopefully leading to a more
751 readable dependency tree.
753 .BR "\-\-update " (\fB\-u\fR)
754 Updates packages to the best version available, which may
755 not always be the highest version number due to masking
756 for testing and development. Package atoms specified on
757 the command line are greedy, meaning that unspecific
758 atoms may match multiple versions of slotted packages.
760 .BR "\-\-use\-ebuild\-visibility [ y | n ]"
761 Use unbuilt ebuild metadata for visibility
762 checks on built packages.
764 .BR "\-\-useoldpkg\-atoms " ATOMS
765 A space separated list of package names or slot atoms. Emerge will prefer
766 matching binary packages over newer unbuilt packages.
768 .BR "\-\-usepkg [ y | n ] (\-k short option)"
769 Tells emerge to use binary packages (from $PKGDIR) if they are available, thus
770 possibly avoiding some time\-consuming compiles. This option is useful for CD
771 installs; you can export PKGDIR=/mnt/cdrom/packages and then use this option to
772 have emerge "pull" binary packages from the CD in order to satisfy dependencies.
774 .BR "\-\-usepkgonly [ y | n ] (\-K short option)"
775 Tells emerge to only use binary packages (from $PKGDIR). All the binary
776 packages must be available at the time of dependency calculation or emerge
777 will simply abort. Portage does not use $PORTDIR when calculating dependency
778 information so all masking information is ignored.
780 .BR "\-\-verbose " (\fB\-v\fR)
781 Tell emerge to run in verbose mode. Currently this flag causes emerge to print
782 out GNU info errors, if any, and to show the USE flags that will be used for
783 each package when pretending. The following symbols are affixed to USE flags
784 in order to indicate their status:
790 Symbol Location Meaning
792 - prefix not enabled (either disabled or removed)
793 * suffix transition to or from the enabled state
794 % suffix newly added or removed
795 () circumfix forced, masked, or removed
796 {} circumfix state is bound to FEATURES settings
799 .BR "\-\-verbose\-main\-repo\-display"
800 In the package merge list display, print ::repository even for main repository.
802 .BR "\-\-with\-bdeps < y | n >"
803 In dependency calculations, pull in build time dependencies
804 that are not strictly required. This defaults to \'n\' for
805 installation actions, meaning they will not be installed, and
806 \'y\' for the \fB\-\-depclean\fR action, meaning they will not be removed.
807 This setting can be added to
808 \fBEMERGE_DEFAULT_OPTS\fR (see make.conf(5)) and later overridden via the
810 .SH "ENVIRONMENT OPTIONS"
812 \fBROOT\fR = \fI[path]\fR
813 Use \fBROOT\fR to specify the target root filesystem to be used for
814 merging packages or ebuilds. This variable can be set via the \fB\-\-root\fR
815 option or in \fBmake.conf\fR(5) (the command line overrides other settings).
819 \fBPORTAGE_CONFIGROOT\fR = \fI[path]\fR
820 Use \fBPORTAGE_CONFIGROOT\fR to specify the location for various portage
822 (see \fBFILES\fR for a detailed list of configuration files). This variable
823 can be set via the \fB\-\-config\-root\fR option.
827 When utilizing \fBemerge\fR with the \fB\-\-pretend\fR and \fB\-\-verbose\fR
828 flags, the output may be a little hard to understand at first. This section
829 explains the abbreviations.
831 .B [blocks B ] app\-text/dos2unix ("app\-text/dos2unix" is blocking app\-text/hd2u\-0.8.0)
832 Dos2unix is Blocking hd2u from being emerged. Blockers are defined when
833 two packages will clobber each others files, or otherwise cause some form
834 of breakage in your system. However, blockers usually do not need to be
835 simultaneously emerged because they usually provide the same functionality.
837 .B [ebuild N ] app\-games/qstat\-25c
838 Qstat is New to your system, and will be emerged for the first time.
840 .B [ebuild NS ] dev-libs/glib-2.4.7
841 You already have a version of glib installed, but a 'new' version in
842 a different SLOT is available.
844 .B [ebuild R ] sys\-apps/sed\-4.0.5
845 Sed 4.0.5 has already been emerged, but if you run the command, then
846 portage will Re\-emerge the specified package (sed in this case).
848 .B [ebuild F ] media\-video/realplayer\-8\-r6
849 The realplayer package requires that you Fetch the sources manually.
850 When you attempt to emerge the package, if the sources are not found,
851 then portage will halt and you will be provided with instructions on how
852 to download the required files.
854 .B [ebuild f ] media\-video/realplayer\-8\-r6
855 The realplayer package's files are already downloaded.
857 .B [ebuild U ] net\-fs/samba\-2.2.8_pre1 [2.2.7a]
858 Samba 2.2.7a has already been emerged and can be Updated to version
861 .B [ebuild UD] media\-libs/libgd\-1.8.4 [2.0.11]
862 Libgd 2.0.11 is already emerged, but if you run the command, then
863 portage will Downgrade to version 1.8.4 for you.
865 This may occur if a newer version of a package has been masked because it is
866 broken or it creates a security risk on your system and a fix has not been
869 Another reason this may occur is if a package you are trying to emerge requires
870 an older version of a package in order to emerge successfully. In this case,
871 libgd 2.x is incompatible with libgd 1.x. This means that packages that were
872 created with libgd 1.x will not compile with 2.x and must downgrade libgd first
873 before they can emerge.
875 .B [ebuild U ] sys\-devel/distcc\-2.16 [2.13\-r1] USE="ipv6* \-gtk \-qt%"
876 Here we see that the make.conf variable \fBUSE\fR affects how this package is
877 built. In this example, ipv6 optional support is enabled and both gtk and qt
878 support are disabled. The asterisk following ipv6 indicates that ipv6 support
879 was disabled the last time this package was installed. The percent sign
880 following qt indicates that the qt option has been added to the package since
881 it was last installed. For information about all \fBUSE\fR symbols, see the
882 \fB\-\-verbose\fR option documentation above.
884 \fB*Note:\fR Flags that haven't changed since the last install are only
885 displayed when you use the \fB\-\-pretend\fR and \fB\-\-verbose\fR options.
886 Using the \fB\-\-quiet\fR option will prevent all information from being
889 .B [ebuild U *] sys\-apps/portage\-2.2.0_alpha6 [2.1.9.25]
890 Portage 2.1.9.25 is installed, but if you run the command, then
891 portage will upgrade to version 2.2.0_alpha6. In this case,
892 the \fB*\fR symbol is displayed, in order to indicate that version
893 2.2.0_alpha6 is masked by missing keyword. This type of masking
894 display is disabled by the \fB\-\-quiet\fR option if the
895 \fB\-\-verbose\fR option is not enabled simultaneously.
896 The following symbols are used to indicate various types
909 \fBNOTE:\fR The unstable keyword symbol (~) will not be shown in cases
910 in which the corresponding unstable keywords have been accepted
911 globally via \fBACCEPT_KEYWORDS\fR.
916 You should almost always precede any package install or update attempt with a
917 \fB\-\-pretend\fR install or update. This lets you see how much will be
918 done, and shows you any blocking packages that you will have to rectify.
919 This goes doubly so for the \fBsystem\fR and \fBworld\fR sets, which can
920 update a large number of packages if the portage tree has been particularly
923 You also want to typically use \fB\-\-update\fR, which ignores packages that
924 are already fully updated but updates those that are not.
926 When you install a package with uninstalled dependencies and do
927 not explicitly state those dependencies in the list of parameters,
928 they will not be added to the world file. If you want them to be
929 detected for world updates, make sure to explicitly list them as
930 parameters to \fBemerge\fR.
932 \fBUSE variables\fR may be specified on the command line to
933 override those specified in the default locations, letting you
934 avoid using some dependencies you may not want to have. \fBUSE
935 flags specified on the command line are NOT remembered\fR. For
936 example, \fBenv USE="\-X \-gnome" emerge mc\fR will emerge mc with
937 those USE settings (on Bourne-compatible shells you may omit the \fBenv\fR
938 part). If you want those USE settings to be more
939 permanent, you can put them in /etc/portage/package.use instead.
941 If \fBemerge \-\-update @system\fR or \fBemerge \-\-update @world\fR
942 fails with an error message, it may be that an ebuild uses some
943 newer feature not present in this version of \fBemerge\fR. You
944 can use \fBemerge \-\-update portage\fR to upgrade to the lastest
945 version, which should support any necessary new features.
946 .SH "MASKED PACKAGES"
947 \fINOTE: Please use caution when using development packages. Problems
948 and bugs resulting from misusing masked packages drains Gentoo
949 developer time. Please be sure you are capable of handling any problems
952 Masks in \fBportage\fR have many uses: they allow a
953 testing period where the packages can be used in live machines; they
954 prevent the use of a package when it will fail; and they mask existing
955 packages that are broken or could pose a security risk. Read below
956 to find out how to unmask in various cases. Also note that if you give
957 \fBemerge\fR an ebuild, then all forms of masking will be ignored and
958 \fBemerge\fR will attempt to emerge the package.
961 When packages are masked for \fBbacktracking\fR, it means that the dependency
962 resolver has temporarily masked them in order to avoid dependency conflicts
963 and/or unsatisfied dependencies. This type of mask is typically accompanied
964 by a message about a missed package update which has been skipped in order to
965 avoid dependency conflicts and/or unsatisfied dependencies.
968 The \fBpackage.mask\fR file primarily blocks the use of packages that cause
969 problems or are known to have issues on different systems. It resides in
970 \fI/usr/portage/profiles\fR.
973 Use the \fBACCEPT_CHOSTS\fR variable in \fBmake.conf\fR(5) to control
974 \fBCHOST\fR acceptance.
977 The \fBEAPI\fR variable in an \fBebuild\fR(5) file is used to mask packages
978 that are not supported by the current version of portage. Packages masked by
979 \fBEAPI\fR can only be installed after portage has been upgraded.
982 The \fBKEYWORDS\fR variable in an \fBebuild\fR file is also used for masking
983 a package still in testing. There are architecture\-specific keywords for
984 each package that let \fBportage\fR know which systems are compatible with
985 the package. Packages which compile on an architecture, but have not been
986 proven to be "stable", are masked with a tilde (\fB~\fR) in front of the
987 architecture name. \fBemerge\fR examines the \fBACCEPT_KEYWORDS\fR environment
988 variable to allow or disallow the emerging of a package masked by
989 \fBKEYWORDS\fR. To inform \fBemerge\fR that it should build these 'testing'
990 versions of packages, you should update your
991 \fI/etc/portage/package.accept_keywords\fR
992 file to list the packages you want the
993 \'testing\' version. See \fBportage\fR(5) for more information.
996 The \fBLICENSE\fR variable in an \fBebuild\fR file can be used to mask
997 packages based on licensing restrictions. \fBemerge\fR examines the
998 \fBACCEPT_LICENSE\fR environment variable to allow or disallow the emerging
999 of a package masked by \fBLICENSE\fR. See \fBmake.conf\fR(5) for information
1000 about \fBACCEPT_LICENSE\fR, and see \fBportage\fR(5) for information about
1001 \fI/etc/portage/package.license\fR.
1004 The \fBPROPERTIES\fR variable in an \fBebuild\fR file can be used to mask
1005 packages based on properties restrictions. \fBemerge\fR examines the
1006 \fBACCEPT_PROPERTIES\fR environment variable to allow or disallow the emerging
1007 of a package masked by \fBPROPERTIES\fR. See \fBmake.conf\fR(5) for information
1008 about \fBACCEPT_PROPERTIES\fR, and see \fBportage\fR(5) for information about
1009 \fI/etc/portage/package.properties\fR. Use the \fB\-\-accept\-properties\fR
1010 option to temporarily override \fBACCEPT_PROPERTIES\fR.
1011 .SH "CONFIGURATION FILES"
1012 Portage has a special feature called "config file protection". The purpose of
1013 this feature is to prevent new package installs from clobbering existing
1014 configuration files. By default, config file protection is turned on for /etc
1015 and the KDE configuration dirs; more may be added in the future.
1017 When Portage installs a file into a protected directory tree like /etc, any
1018 existing files will not be overwritten. If a file of the same name already
1019 exists, Portage will change the name of the to\-be\-installed file from 'foo' to
1020 \'._cfg0000_foo\'. If \'._cfg0000_foo\' already exists, this name becomes
1021 \'._cfg0001_foo\', etc. In this way, existing files are not overwritten,
1022 allowing the administrator to manually merge the new config files and avoid any
1025 In addition to protecting overwritten files, Portage will not delete any files
1026 from a protected directory when a package is unmerged. While this may be a
1027 little bit untidy, it does prevent potentially valuable config files from being
1028 deleted, which is of paramount importance.
1030 Protected directories are set using the \fICONFIG_PROTECT\fR variable, normally
1031 defined in make.globals. Directory exceptions to the CONFIG_PROTECTed
1032 directories can be specified using the \fICONFIG_PROTECT_MASK\fR variable. To find
1033 files that need to be updated in /etc, type \fBfind /etc \-iname \'._cfg????_*\'\fR.
1035 You can disable this feature by setting \fICONFIG_PROTECT="\-*"\fR in /etc/make.conf.
1036 Then, Portage will mercilessly auto\-update your config files. Alternatively,
1037 you can leave Config File Protection on but tell Portage that it can overwrite
1038 files in certain specific /etc subdirectories. For example, if you wanted
1039 Portage to automatically update your rc scripts and your wget configuration,
1040 but didn't want any other changes made without your explicit approval, you'd
1041 add this to /etc/make.conf:
1043 .I CONFIG_PROTECT_MASK="/etc/wget /etc/rc.d"
1045 Tools such as dispatch\-conf, cfg\-update, and etc\-update are also available to
1046 aid in the merging of these files. They provide interactive merging and can
1047 auto\-merge trivial changes.
1048 .SH "REPORTING BUGS"
1049 Please report any bugs you encounter through our website:
1051 \fBhttp://bugs.gentoo.org/\fR
1053 Please include the output of \fBemerge \-\-info\fR when you submit your
1057 Daniel Robbins <drobbins@gentoo.org>
1058 Geert Bevin <gbevin@gentoo.org>
1059 Achim Gottinger <achim@gentoo.org>
1060 Nicholas Jones <carpaski@gentoo.org>
1061 Phil Bordelon <phil@thenexusproject.org>
1062 Mike Frysinger <vapier@gentoo.org>
1063 Marius Mauch <genone@gentoo.org>
1064 Jason Stubbs <jstubbs@gentoo.org>
1065 Brian Harring <ferringb@gmail.com>
1066 Zac Medico <zmedico@gentoo.org>
1069 Here is a common list of files you will probably be interested in. For a
1070 complete listing, please refer to the \fBportage\fR(5) man page.
1072 .B /usr/share/portage/config/sets/
1073 Contains the default set configuration.
1075 .B /var/lib/portage/world
1076 Contains a list of all user\-specified packages. You can safely edit
1077 this file, adding packages that you want to be considered in \fBworld\fR
1078 set updates and removing those that you do not want to be considered.
1080 .B /var/lib/portage/world_sets
1081 This is like the world file but instead of package atoms it contains
1082 packages sets which always begin with the \fB@\fR character. Use
1083 \fB/etc/portage/sets/\fR to define user package sets.
1086 Contains variables for the build process, overriding those in
1089 .B /etc/portage/color.map
1090 Contains variables customizing colors.
1092 .B /etc/portage/sets/
1093 Contains user package set definitions (see \fBportage\fR(5)).
1095 .B /etc/dispatch\-conf.conf
1096 Contains settings to handle automatic updates/backups of configuration
1099 .B /etc/portage/make.profile/make.defaults
1100 Contains profile\-specific variables for the build process. \fBDo not
1103 .B /usr/portage/profiles/use.desc
1104 Contains the master list of USE flags with descriptions of their
1105 functions. \fBDo not edit this file\fR.
1107 .B /etc/portage/make.profile/virtuals
1108 Contains a list of default packages used to resolve virtual dependencies.
1109 \fBDo not edit this file\fR.
1111 .B /etc/portage/make.profile/packages
1112 Contains a list of packages used for the base system. The \fBsystem\fR
1113 and \fBworld\fR sets consult this file. \fBDo not edit this file\fR.
1115 .B /usr/share/portage/config/make.globals
1116 Contains the default variables for the build process. \fBDo not edit
1119 .BR "emerge \-\-help",
1127 A number of helper applications reside in \fI/usr/lib/portage/bin\fR.
1129 The \fBapp\-portage/gentoolkit\fR package contains useful scripts such as
1130 \fBequery\fR (a package query tool).
projects / portage.git / blob