1 .TH "EMERGE" "1" "Feb 2013" "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
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. If FEATURES="preserve\-libs" is
433 enabled in \fBmake.conf\fR(5), and preserve\-libs is not restricted
434 for any of the packages selected for removal, then this option is
435 ignored because any libraries that have consumers will simply be
439 Prevent corruption from being noticed. The `repoman manifest` command is the
440 preferred way to generate manifests and it is capable of doing an entire
441 repository or category at once (see \fBrepoman\fR(1)).
443 .BR "\-\-dynamic\-deps < y | n >"
444 In dependency calculations, substitute the dependencies of installed
445 packages with the dependencies of corresponding unbuilt ebuilds from
446 source repositories. This causes the effective dependencies of
447 installed packages to vary dynamically when source ebuild dependencies
448 are modified. This option is enabled by default.
451 If you want to disable \-\-dynamic\-deps, then it may be necessary to
452 first run \fBfixpackages\fR(1) in order to get the best results. The
453 \fBfixpackages\fR(1) command performs two different operations that can
454 also be performed separately by the `emaint \-\-fix moveinst` and
455 `emaint \-\-fix movebin` commands (see \fBemaint\fR(1)).
457 .BR "\-\-emptytree " (\fB\-e\fR)
458 Reinstalls target atoms and their entire deep
459 dependency tree, as though no packages are currently
460 installed. You should run this with \fB\-\-pretend\fR
461 first to make sure the result is what you expect.
463 .BR "\-\-exclude " ATOMS
464 A space separated list of package names or slot atoms.
465 Emerge won't install any ebuild or binary package that
466 matches any of the given package atoms.
468 .BR "\-\-fail\-clean [ y | n ]"
469 Clean up temporary files after a build failure. This is
470 particularly useful if you have \fBPORTAGE_TMPDIR\fR on
471 tmpfs. If this option is enabled, you probably also want
472 to enable \fBPORT_LOGDIR\fR (see \fBmake.conf\fR(5)) in
473 order to save the build log.
475 .BR "\-\-fetchonly " (\fB\-f\fR)
476 Instead of doing any package building, just perform fetches for all
477 packages (fetch things from SRC_URI based upon USE setting).
479 .BR "\-\-fetch\-all\-uri " (\fB\-F\fR)
480 Instead of doing any package building, just perform fetches for all
481 packages (fetch everything in SRC_URI regardless of USE setting).
483 .BR "\-\-getbinpkg [ y | n ] (\-g short option)"
484 Using the server and location defined in \fIPORTAGE_BINHOST\fR (see
485 \fBmake.conf\fR(5)), portage will download the information from each binary
486 package found and it will use that information to help build the dependency
487 list. This option implies \fB\-k\fR. (Use \fB\-gK\fR for binary\-only
490 .BR "\-\-getbinpkgonly [ y | n ] (\-G short option)"
491 This option is identical to \fB\-g\fR, as above, except binaries from the
492 remote server are preferred over local packages if they are not identical.
494 .BR "\-\-ignore-default-opts"
495 Causes \fIEMERGE_DEFAULT_OPTS\fR (see \fBmake.conf\fR(5)) to be ignored.
497 .BR "\-\-ignore\-built\-slot\-operator\-deps < y | n >"
498 Ignore the slot/sub\-slot := operator parts of dependencies that have
499 been recorded when packages where built. This option is intended
500 only for debugging purposes, and it only affects built packages
501 that specify slot/sub\-slot := operator dependencies which are
502 supported beginning with \fBEAPI 5\fR.
504 .BR "-j [JOBS], \-\-jobs[=JOBS]"
505 Specifies the number of packages to build simultaneously. If this option is
506 given without an argument, emerge will not limit the number of jobs that can
507 run simultaneously. Also see the related \fB\-\-load\-average\fR option.
508 Similarly to the \-\-quiet\-build option, the \-\-jobs option causes all
509 build output to be redirected to logs.
510 Note that interactive packages currently force a setting
511 of \fI\-\-jobs=1\fR. This issue can be temporarily avoided
512 by specifying \fI\-\-accept\-properties=\-interactive\fR.
514 .BR "\-\-keep\-going [ y | n ]"
515 Continue as much as possible after an error. When an error occurs,
516 dependencies are recalculated for remaining packages and any with
517 unsatisfied dependencies are automatically dropped. Also see
518 the related \fB\-\-skipfirst\fR option.
520 .BR "\-\-load\-average [LOAD]"
521 Specifies that no new builds should be started if there are other builds
522 running and the load average is at least LOAD (a floating-point number).
523 With no argument, removes a previous load limit.
524 This option is recommended for use in combination with \fB\-\-jobs\fR in
525 order to avoid excess load. See \fBmake\fR(1) for information about
526 analogous options that should be configured via \fBMAKEOPTS\fR in
529 .BR "\-\-misspell\-suggestions < y | n >"
530 Enable or disable misspell suggestions. By default, emerge will show
531 a list of packages with similar names when a package doesn't exist.
532 The \fIEMERGE_DEFAULT_OPTS\fR variable may be used to disable this
535 .BR "\-\-newuse " (\fB\-N\fR)
536 Tells emerge to include installed packages where USE
537 flags have changed since compilation. This option
538 also implies the \fB\-\-selective\fR option.
539 USE flag changes include:
541 A USE flag was added to a package.
542 A USE flag was removed from a package.
543 A USE flag was turned on for a package.
544 A USE flag was turned off for a package.
546 USE flags may be toggled by your profile as well as your USE and package.use
547 settings. If you would like to skip rebuilds for which disabled flags have
548 been added to or removed from IUSE, see the related
549 \fB\-\-changed\-use\fR option. If you would like to skip rebuilds for
550 specific packages, see the \fB\-\-exclude\fR option.
552 NOTE: This option ignores the state of the "test" USE flag, since that flag
553 has a special binding to FEATURES="test" (see \fBmake.conf\fR(5) for more
554 information about \fBFEATURES\fR settings).
557 Causes portage to disregard merge records indicating that a config file
558 inside of a \fBCONFIG_PROTECT\fR directory has been merged already. Portage
559 will normally merge those files only once to prevent the user from
560 dealing with the same config multiple times. This flag will cause the
561 file to always be merged.
563 .BR "\-\-nodeps " (\fB\-O\fR)
564 Merges specified packages without merging any dependencies. Note that
565 the build may fail if the dependencies aren't satisfied.
567 .BR "\-\-noreplace " (\fB\-n\fR)
568 Skips the packages specified on the command\-line that have already
569 been installed. Without this option, any package atoms or package sets
570 you specify on the command\-line \fBwill\fR cause Portage to remerge
571 the package, even if it is already installed. Note that Portage will
572 not remerge dependencies by default.
575 Disables the spinner for the session. The spinner is active when the
576 terminal device is determined to be a TTY. This flag disables it regardless.
578 .BR "\-\-usepkg\-exclude " ATOMS
579 A space separated list of package names or slot atoms. Emerge will ignore
580 matching binary packages.
582 .BR "\-\-rebuild\-exclude " ATOMS
583 A space separated list of package names or slot atoms. Emerge will not rebuild
584 matching packages due to \fB\-\-rebuild\fR.
586 .BR "\-\-rebuild\-ignore " ATOMS
587 A space separated list of package names or slot atoms. Emerge will not rebuild
588 packages that depend on matching packages due to \fB\-\-rebuild\fR.
590 .BR "\-\-oneshot " (\fB\-1\fR)
591 Emerge as normal, but do not add the packages to the world file
594 .BR "\-\-onlydeps " (\fB\-o\fR)
595 Only merge (or pretend to merge) the dependencies of the packages
596 specified, not the packages themselves.
598 .BR "\-\-package\-moves [ y | n ]"
599 Perform package moves when necessary. This option is enabled
600 by default. Package moves are typically applied immediately
601 after a \fB\-\-sync\fR action. They are applied in an
602 incremental fashion, using only the subset of the history of
603 package moves which have been added or modified since the
604 previous application of package moves.
606 \fBWARNING:\fR This option
607 should remain enabled under normal circumstances.
608 Do not disable it unless you know what you are
611 \fBNOTE:\fR The \fBfixpackages\fR(1) command can be used to
612 exhaustively apply the entire history of package moves,
613 regardless of whether or not any of the package moves have
614 been previously applied.
616 .BR "\-\-pretend " (\fB\-p\fR)
617 Instead of actually performing the merge, simply display what *would*
618 have been installed if \fB\-\-pretend\fR weren't used. Using \fB\-\-pretend\fR
619 is strongly recommended before installing an unfamiliar package. In
624 N new (not yet installed)
625 S new SLOT installation (side-by-side versions)
626 U updating (to another version)
627 D downgrading (best version seems lower)
628 r reinstall (forced for some reason, possibly due to slot or sub\-slot)
629 R replacing (remerging same version)
630 F fetch restricted (must be manually downloaded)
631 f fetch restricted (already downloaded)
632 I interactive (requires user input)
633 B blocked by another package (unresolved conflict)
634 b blocked by another package (automatically resolved conflict)
637 .BR "\-\-quiet [ y | n ] (\-q short option)"
638 Results may vary, but the general outcome is a reduced or condensed
639 output from portage's displays.
641 .BR "\-\-quiet\-build [ y | n ]"
642 Redirect all build output to logs alone, and do not display it on
643 stdout. If a build failure occurs for a single package, the build
644 log will be automatically displayed on stdout (unless the
645 \fI\-\-quiet\-fail\fR option is enabled). If there are multiple
646 build failures (due to options like \-\-keep\-going or \-\-jobs),
647 then the content of the log files will not be displayed, and instead
648 the paths of the log files will be displayed together with the
649 corresponding die messages.
650 Note that interactive packages currently force all build output to
651 be displayed on stdout. This issue can be temporarily avoided
652 by specifying \fI\-\-accept\-properties=\-interactive\fR.
654 .BR "\-\-quiet\-fail [ y | n ]"
655 Suppresses display of the build log on stdout when build output is hidden
656 due to options such as \fI\-\-jobs\fR, \fI\-\-quiet\fR, or
657 \fI\-\-quiet\-build\fR. Only the die message and the path of the build log
658 will be displayed on stdout.
660 .BR "\-\-quiet\-repo\-display"
661 In the package merge list display, suppress ::repository output, and
662 instead use numbers to indicate which repositories package come from.
664 .BR \-\-quiet\-unmerge\-warn
665 Disable the warning message that's shown prior to
666 \fB\-\-unmerge\fR actions. This option is intended
667 to be set in the \fBmake.conf\fR(5)
668 \fBEMERGE_DEFAULT_OPTS\fR variable.
670 .BR "\-\-rebuild\-if\-new\-slot [ y | n ]"
671 Automatically rebuild or reinstall packages when slot/sub\-slot :=
672 operator dependencies can be satisfied by a newer slot, so that
673 older packages slots will become eligible for removal by the
674 \-\-depclean action as soon as possible. This option only
675 affects packages that specify slot/sub\-slot := dependencies
676 which are supported beginning with \fBEAPI 5\fR.
677 Since this option requires
678 checking of reverse dependencies, it enables \-\-complete\-graph
679 mode whenever a new slot is installed. This option is enabled by
682 NOTE: If you want to skip all rebuilds involving slot\-operator
683 dependecies (including those that involve sub\-slot changes alone),
684 then \fI\-\-ignore\-built\-slot\-operator\-deps=y\fR is the option
685 that you are looking for, since \fI\-\-rebuild\-if\-new\-slot\fR
686 does not affect rebuilds triggered by sub\-slot changes alone.
688 .BR "\-\-rebuild\-if\-new\-rev [ y | n ]"
689 Rebuild packages when build\-time dependencies are built from source, if the
690 dependency is not already installed with the same version and revision.
692 .BR "\-\-rebuild\-if\-new\-ver [ y | n ]"
693 Rebuild packages when build\-time dependencies are built from source, if the
694 dependency is not already installed with the same version. Revision numbers
697 .BR "\-\-rebuild\-if\-unbuilt [ y | n ]"
698 Rebuild packages when build\-time dependencies are built from source.
700 .BR "\-\-rebuilt\-binaries [ y | n ]"
701 Replace installed packages with binary packages that have
702 been rebuilt. Rebuilds are detected by comparison of
703 BUILD_TIME package metadata. This option is enabled
704 automatically when using binary packages
705 (\fB\-\-usepkgonly\fR or \fB\-\-getbinpkgonly\fR) together with
706 \fB\-\-update\fR and \fB\-\-deep\fR.
708 .BR "\-\-rebuilt\-binaries\-timestamp=TIMESTAMP"
709 This option modifies emerge's behaviour only if
710 \fB\-\-rebuilt\-binaries\fR is given. Only binaries that
711 have a BUILD_TIME that is larger than the given TIMESTAMP
712 and that is larger than that of the installed package will
713 be considered by the rebuilt\-binaries logic.
715 .BR "\-\-reinstall changed\-use"
716 This is an alias for \fB\-\-changed\-use\fR.
718 .BR "\-\-reinstall\-atoms " ATOMS
719 A space separated list of package names or slot atoms. Emerge will treat
720 matching packages as if they are not installed, and reinstall them if
724 Set the \fBROOT\fR environment variable.
726 .BR "\-\-root\-deps[=rdeps]"
727 If no argument is given then build\-time dependencies of packages for
728 \fBROOT\fR are installed to \fBROOT\fR instead of /.
729 If the \fBrdeps\fR argument is given then discard all build\-time dependencies
730 of packages for \fBROOT\fR.
731 This option is only meaningful when used together with \fBROOT\fR and it should
732 not be enabled under normal circumstances!
734 Does not affect EAPIs that support \fBHDEPEND\fR.
735 Experimental \fBEAPI 5-hdepend\fR provides \fBHDEPEND\fR as a new
736 means to adjust installation into "\fI/\fR" and \fBROOT\fR.
737 If ebuilds using EAPIs which \fIdo not\fR support \fBHDEPEND\fR are built in
738 the same \fBemerge\fR run as those using EAPIs which \fIdo\fR support
739 \fBHDEPEND\fR, this option affects only the former.
741 .BR "\-\-select [ y | n ] (\-w short option)"
742 Add specified packages to the world set (inverse of
743 \fB\-\-oneshot\fR). This is useful if you want to
744 use \fBEMERGE_DEFAULT_OPTS\fR to make
745 \fB\-\-oneshot\fR behavior default.
747 .BR "\-\-selective [ y | n ]"
748 This is identical to the \fB\-\-noreplace\fR option.
749 Some options, such as \fB\-\-update\fR, imply \fB\-\-selective\fR.
750 Use \fB\-\-selective=n\fR if you want to forcefully disable
751 \fB\-\-selective\fR, regardless of options like \fB\-\-changed\-use\fR,
752 \fB\-\-newuse\fR, \fB\-\-noreplace\fR, or \fB\-\-update\fR.
755 This option is only valid when used with \fB\-\-resume\fR. It removes the
756 first package in the resume list. Dependencies are recalculated for
757 remaining packages and any that have unsatisfied dependencies or are
758 masked will be automatically dropped. Also see the related
759 \fB\-\-keep\-going\fR option.
761 .BR "\-\-tree " (\fB\-t\fR)
762 Shows the dependency tree for the given target by indenting dependencies.
763 This is only really useful in combination with \fB\-\-emptytree\fR or
764 \fB\-\-update\fR and \fB\-\-deep\fR.
766 .BR "\-\-unordered\-display"
767 By default the displayed merge list is sorted using the
768 order in which the packages will be merged. When
769 \fB\-\-tree\fR is used together with this option, this
770 constraint is removed, hopefully leading to a more
771 readable dependency tree.
773 .BR "\-\-update " (\fB\-u\fR)
774 Updates packages to the best version available, which may
775 not always be the highest version number due to masking
776 for testing and development. Package atoms specified on
777 the command line are greedy, meaning that unspecific
778 atoms may match multiple versions of slotted packages.
780 .BR "\-\-use\-ebuild\-visibility [ y | n ]"
781 Use unbuilt ebuild metadata for visibility
782 checks on built packages.
784 .BR "\-\-useoldpkg\-atoms " ATOMS
785 A space separated list of package names or slot atoms. Emerge will prefer
786 matching binary packages over newer unbuilt packages.
788 .BR "\-\-usepkg [ y | n ] (\-k short option)"
789 Tells emerge to use binary packages (from $PKGDIR) if they are available, thus
790 possibly avoiding some time\-consuming compiles. This option is useful for CD
791 installs; you can export PKGDIR=/mnt/cdrom/packages and then use this option to
792 have emerge "pull" binary packages from the CD in order to satisfy dependencies.
794 .BR "\-\-usepkgonly [ y | n ] (\-K short option)"
795 Tells emerge to only use binary packages (from $PKGDIR). All the binary
796 packages must be available at the time of dependency calculation or emerge
797 will simply abort. Portage does not use $PORTDIR when calculating dependency
798 information so all masking information is ignored.
800 .BR "\-\-verbose [ y | n ] (\-v short option)"
801 Tell emerge to run in verbose mode. Currently this flag causes emerge to print
802 out GNU info errors, if any, and to show the USE flags that will be used for
803 each package when pretending. The following symbols are affixed to USE flags
804 in order to indicate their status:
810 Symbol Location Meaning
812 - prefix not enabled (either disabled or removed)
813 * suffix transition to or from the enabled state
814 % suffix newly added or removed
815 () circumfix forced, masked, or removed
816 {} circumfix state is bound to FEATURES settings
819 .BR "\-\-verbose\-main\-repo\-display"
820 In the package merge list display, print ::repository even for main repository.
822 .BR "\-\-with\-bdeps < y | n >"
823 In dependency calculations, pull in build time dependencies
824 that are not strictly required. This defaults to \'n\' for
825 installation actions, meaning they will not be installed, and
826 \'y\' for the \fB\-\-depclean\fR action, meaning they will not be removed.
827 This setting can be added to
828 \fBEMERGE_DEFAULT_OPTS\fR (see make.conf(5)) and later overridden via the
830 .SH "ENVIRONMENT OPTIONS"
832 \fBROOT\fR = \fI[path]\fR
833 Use \fBROOT\fR to specify the target root filesystem to be used for
834 merging packages or ebuilds. This variable can be set via the \fB\-\-root\fR
835 option or in \fBmake.conf\fR(5) (the command line overrides other settings).
839 \fBPORTAGE_CONFIGROOT\fR = \fI[path]\fR
840 Use \fBPORTAGE_CONFIGROOT\fR to specify the location for various portage
842 (see \fBFILES\fR for a detailed list of configuration files). This variable
843 can be set via the \fB\-\-config\-root\fR option.
847 When utilizing \fBemerge\fR with the \fB\-\-pretend\fR and \fB\-\-verbose\fR
848 flags, the output may be a little hard to understand at first. This section
849 explains the abbreviations.
851 .B [blocks B ] app\-text/dos2unix ("app\-text/dos2unix" is blocking app\-text/hd2u\-0.8.0)
852 Dos2unix is Blocking hd2u from being emerged. Blockers are defined when
853 two packages will clobber each others files, or otherwise cause some form
854 of breakage in your system. However, blockers usually do not need to be
855 simultaneously emerged because they usually provide the same functionality.
857 .B [ebuild N ] app\-games/qstat\-25c
858 Qstat is New to your system, and will be emerged for the first time.
860 .B [ebuild NS ] dev-libs/glib-2.4.7
861 You already have a version of glib installed, but a 'new' version in
862 a different SLOT is available.
864 .B [ebuild R ] sys\-apps/sed\-4.0.5
865 Sed 4.0.5 has already been emerged, but if you run the command, then
866 portage will Re\-emerge the specified package (sed in this case).
868 .B [ebuild F ] media\-video/realplayer\-8\-r6
869 The realplayer package requires that you Fetch the sources manually.
870 When you attempt to emerge the package, if the sources are not found,
871 then portage will halt and you will be provided with instructions on how
872 to download the required files.
874 .B [ebuild f ] media\-video/realplayer\-8\-r6
875 The realplayer package's files are already downloaded.
877 .B [ebuild U ] net\-fs/samba\-2.2.8_pre1 [2.2.7a]
878 Samba 2.2.7a has already been emerged and can be Updated to version
881 .B [ebuild UD] media\-libs/libgd\-1.8.4 [2.0.11]
882 Libgd 2.0.11 is already emerged, but if you run the command, then
883 portage will Downgrade to version 1.8.4 for you.
885 This may occur if a newer version of a package has been masked because it is
886 broken or it creates a security risk on your system and a fix has not been
889 Another reason this may occur is if a package you are trying to emerge requires
890 an older version of a package in order to emerge successfully. In this case,
891 libgd 2.x is incompatible with libgd 1.x. This means that packages that were
892 created with libgd 1.x will not compile with 2.x and must downgrade libgd first
893 before they can emerge.
895 .B [ebuild U ] sys\-devel/distcc\-2.16 [2.13\-r1] USE="ipv6* \-gtk \-qt%"
896 Here we see that the make.conf variable \fBUSE\fR affects how this package is
897 built. In this example, ipv6 optional support is enabled and both gtk and qt
898 support are disabled. The asterisk following ipv6 indicates that ipv6 support
899 was disabled the last time this package was installed. The percent sign
900 following qt indicates that the qt option has been added to the package since
901 it was last installed. For information about all \fBUSE\fR symbols, see the
902 \fB\-\-verbose\fR option documentation above.
904 \fB*Note:\fR Flags that haven't changed since the last install are only
905 displayed when you use the \fB\-\-pretend\fR and \fB\-\-verbose\fR options.
906 Using the \fB\-\-quiet\fR option will prevent all information from being
909 .B [ebuild r U ] dev\-libs/icu\-50.1.1:0/50.1.1 [50.1\-r2:0/50.1]
910 Icu 50.1\-r2 has already been emerged and can be Updated to version
911 50.1.1. The \fBr\fR symbol indicates that a sub\-slot change (from 50.1
912 to 50.1.1 in this case) will force packages having slot\-operator
913 dependencies on it to be rebuilt (as libxml2 will be rebuilt in the next
916 .B [ebuild rR ] dev\-libs/libxml2\-2.9.0\-r1:2 USE="icu"
917 Libxml2 2.9.0\-r1 has already been emerged, but if you run the command,
918 then portage will Re\-emerge it in order to satisfy a slot\-operator
919 dependency which forces it to be rebuilt when the icu sub\-slot changes
920 (as it changed in the previous example).
922 .B [ebuild U *] sys\-apps/portage\-2.2.0_alpha6 [2.1.9.25]
923 Portage 2.1.9.25 is installed, but if you run the command, then
924 portage will upgrade to version 2.2.0_alpha6. In this case,
925 the \fB*\fR symbol is displayed, in order to indicate that version
926 2.2.0_alpha6 is masked by missing keyword. This type of masking
927 display is disabled by the \fB\-\-quiet\fR option if the
928 \fB\-\-verbose\fR option is not enabled simultaneously.
929 The following symbols are used to indicate various types
942 \fBNOTE:\fR The unstable keyword symbol (~) will not be shown in cases
943 in which the corresponding unstable keywords have been accepted
944 globally via \fBACCEPT_KEYWORDS\fR.
949 You should almost always precede any package install or update attempt with a
950 \fB\-\-pretend\fR install or update. This lets you see how much will be
951 done, and shows you any blocking packages that you will have to rectify.
952 This goes doubly so for the \fBsystem\fR and \fBworld\fR sets, which can
953 update a large number of packages if the portage tree has been particularly
956 You also want to typically use \fB\-\-update\fR, which ignores packages that
957 are already fully updated but updates those that are not.
959 When you install a package with uninstalled dependencies and do
960 not explicitly state those dependencies in the list of parameters,
961 they will not be added to the world file. If you want them to be
962 detected for world updates, make sure to explicitly list them as
963 parameters to \fBemerge\fR.
965 \fBUSE variables\fR may be specified on the command line to
966 override those specified in the default locations, letting you
967 avoid using some dependencies you may not want to have. \fBUSE
968 flags specified on the command line are NOT remembered\fR. For
969 example, \fBenv USE="\-X \-gnome" emerge mc\fR will emerge mc with
970 those USE settings (on Bourne-compatible shells you may omit the \fBenv\fR
971 part). If you want those USE settings to be more
972 permanent, you can put them in /etc/portage/package.use instead.
974 If \fBemerge \-\-update @system\fR or \fBemerge \-\-update @world\fR
975 fails with an error message, it may be that an ebuild uses some
976 newer feature not present in this version of \fBemerge\fR. You
977 can use \fBemerge \-\-update portage\fR to upgrade to the lastest
978 version, which should support any necessary new features.
979 .SH "MASKED PACKAGES"
980 \fINOTE: Please use caution when using development packages. Problems
981 and bugs resulting from misusing masked packages drains Gentoo
982 developer time. Please be sure you are capable of handling any problems
985 Masks in \fBportage\fR have many uses: they allow a
986 testing period where the packages can be used in live machines; they
987 prevent the use of a package when it will fail; and they mask existing
988 packages that are broken or could pose a security risk. Read below
989 to find out how to unmask in various cases. Also note that if you give
990 \fBemerge\fR an ebuild, then all forms of masking will be ignored and
991 \fBemerge\fR will attempt to emerge the package.
994 When packages are masked for \fBbacktracking\fR, it means that the dependency
995 resolver has temporarily masked them in order to avoid dependency conflicts
996 and/or unsatisfied dependencies. This type of mask is typically accompanied
997 by a message about a missed package update which has been skipped in order to
998 avoid dependency conflicts and/or unsatisfied dependencies.
1001 The \fBpackage.mask\fR file primarily blocks the use of packages that cause
1002 problems or are known to have issues on different systems. It resides in
1003 \fI/usr/portage/profiles\fR.
1006 Use the \fBACCEPT_CHOSTS\fR variable in \fBmake.conf\fR(5) to control
1007 \fBCHOST\fR acceptance.
1010 The \fBEAPI\fR variable in an \fBebuild\fR(5) file is used to mask packages
1011 that are not supported by the current version of portage. Packages masked by
1012 \fBEAPI\fR can only be installed after portage has been upgraded.
1015 The \fBKEYWORDS\fR variable in an \fBebuild\fR file is also used for masking
1016 a package still in testing. There are architecture\-specific keywords for
1017 each package that let \fBportage\fR know which systems are compatible with
1018 the package. Packages which compile on an architecture, but have not been
1019 proven to be "stable", are masked with a tilde (\fB~\fR) in front of the
1020 architecture name. \fBemerge\fR examines the \fBACCEPT_KEYWORDS\fR environment
1021 variable to allow or disallow the emerging of a package masked by
1022 \fBKEYWORDS\fR. To inform \fBemerge\fR that it should build these 'testing'
1023 versions of packages, you should update your
1024 \fI/etc/portage/package.accept_keywords\fR
1025 file to list the packages you want the
1026 \'testing\' version. See \fBportage\fR(5) for more information.
1029 The \fBLICENSE\fR variable in an \fBebuild\fR file can be used to mask
1030 packages based on licensing restrictions. \fBemerge\fR examines the
1031 \fBACCEPT_LICENSE\fR environment variable to allow or disallow the emerging
1032 of a package masked by \fBLICENSE\fR. See \fBmake.conf\fR(5) for information
1033 about \fBACCEPT_LICENSE\fR, and see \fBportage\fR(5) for information about
1034 \fI/etc/portage/package.license\fR.
1037 The \fBPROPERTIES\fR variable in an \fBebuild\fR file can be used to mask
1038 packages based on properties restrictions. \fBemerge\fR examines the
1039 \fBACCEPT_PROPERTIES\fR environment variable to allow or disallow the emerging
1040 of a package masked by \fBPROPERTIES\fR. See \fBmake.conf\fR(5) for information
1041 about \fBACCEPT_PROPERTIES\fR, and see \fBportage\fR(5) for information about
1042 \fI/etc/portage/package.properties\fR. Use the \fB\-\-accept\-properties\fR
1043 option to temporarily override \fBACCEPT_PROPERTIES\fR.
1044 .SH "CONFIGURATION FILES"
1045 Portage has a special feature called "config file protection". The purpose of
1046 this feature is to prevent new package installs from clobbering existing
1047 configuration files. By default, config file protection is turned on for /etc
1048 and the KDE configuration dirs; more may be added in the future.
1050 When Portage installs a file into a protected directory tree like /etc, any
1051 existing files will not be overwritten. If a file of the same name already
1052 exists, Portage will change the name of the to\-be\-installed file from 'foo' to
1053 \'._cfg0000_foo\'. If \'._cfg0000_foo\' already exists, this name becomes
1054 \'._cfg0001_foo\', etc. In this way, existing files are not overwritten,
1055 allowing the administrator to manually merge the new config files and avoid any
1058 In addition to protecting overwritten files, Portage will not delete any files
1059 from a protected directory when a package is unmerged. While this may be a
1060 little bit untidy, it does prevent potentially valuable config files from being
1061 deleted, which is of paramount importance.
1063 Protected directories are set using the \fICONFIG_PROTECT\fR variable, normally
1064 defined in make.globals. Directory exceptions to the CONFIG_PROTECTed
1065 directories can be specified using the \fICONFIG_PROTECT_MASK\fR variable. To find
1066 files that need to be updated in /etc, type \fBfind /etc \-iname \'._cfg????_*\'\fR.
1068 You can disable this feature by setting \fICONFIG_PROTECT="\-*"\fR in \fBmake.conf\fR(5).
1069 Then, Portage will mercilessly auto\-update your config files. Alternatively,
1070 you can leave Config File Protection on but tell Portage that it can overwrite
1071 files in certain specific /etc subdirectories. For example, if you wanted
1072 Portage to automatically update your rc scripts and your wget configuration,
1073 but didn't want any other changes made without your explicit approval, you'd
1074 add this to \fBmake.conf\fR(5):
1076 .I CONFIG_PROTECT_MASK="/etc/wget /etc/rc.d"
1078 Tools such as dispatch\-conf, cfg\-update, and etc\-update are also available to
1079 aid in the merging of these files. They provide interactive merging and can
1080 auto\-merge trivial changes.
1081 .SH "REPORTING BUGS"
1082 Please report any bugs you encounter through our website:
1084 \fBhttp://bugs.gentoo.org/\fR
1086 Please include the output of \fBemerge \-\-info\fR when you submit your
1090 Daniel Robbins <drobbins@gentoo.org>
1091 Geert Bevin <gbevin@gentoo.org>
1092 Achim Gottinger <achim@gentoo.org>
1093 Nicholas Jones <carpaski@gentoo.org>
1094 Phil Bordelon <phil@thenexusproject.org>
1095 Mike Frysinger <vapier@gentoo.org>
1096 Marius Mauch <genone@gentoo.org>
1097 Jason Stubbs <jstubbs@gentoo.org>
1098 Brian Harring <ferringb@gmail.com>
1099 Zac Medico <zmedico@gentoo.org>
1102 Here is a common list of files you will probably be interested in. For a
1103 complete listing, please refer to the \fBportage\fR(5) man page.
1105 .B /usr/share/portage/config/sets/
1106 Contains the default set configuration.
1108 .B /var/lib/portage/world
1109 Contains a list of all user\-specified packages. You can safely edit
1110 this file, adding packages that you want to be considered in \fBworld\fR
1111 set updates and removing those that you do not want to be considered.
1113 .B /var/lib/portage/world_sets
1114 This is like the world file but instead of package atoms it contains
1115 packages sets which always begin with the \fB@\fR character. Use
1116 \fB/etc/portage/sets/\fR to define user package sets.
1118 .B /etc/portage/make.conf
1119 Contains variables for the build process, overriding those in
1122 .B /etc/portage/color.map
1123 Contains variables customizing colors.
1125 .B /etc/portage/sets/
1126 Contains user package set definitions (see \fBportage\fR(5)).
1128 .B /etc/dispatch\-conf.conf
1129 Contains settings to handle automatic updates/backups of configuration
1132 .B /etc/portage/make.profile/make.defaults
1133 Contains profile\-specific variables for the build process. \fBDo not
1136 .B /usr/portage/profiles/use.desc
1137 Contains the master list of USE flags with descriptions of their
1138 functions. \fBDo not edit this file\fR.
1140 .B /etc/portage/make.profile/virtuals
1141 Contains a list of default packages used to resolve virtual dependencies.
1142 \fBDo not edit this file\fR.
1144 .B /etc/portage/make.profile/packages
1145 Contains a list of packages used for the base system. The \fBsystem\fR
1146 and \fBworld\fR sets consult this file. \fBDo not edit this file\fR.
1148 .B /usr/share/portage/config/make.globals
1149 Contains the default variables for the build process. \fBDo not edit
1152 .BR "emerge \-\-help",
1160 A number of helper applications reside in \fI/usr/lib/portage/bin\fR.
1162 The \fBapp\-portage/gentoolkit\fR package contains useful scripts such as
1163 \fBequery\fR (a package query tool).
projects / portage.git / blob