1 .TH "PORTAGE" "5" "May 2011" "Portage VERSION" "Portage"
3 portage \- the heart of Gentoo
5 The current portage code uses many different configuration files, most of which
6 are unknown to users and normal developers. Here we will try to collect all
7 the odds and ends so as to help users more effectively utilize portage. This
8 is a reference only for files which do not already have a man page.
10 All files in the make.profile directory may be tweaked via parent profiles
11 when using cascading profiles. For more info, please see
12 http://www.gentoo.org/proj/en/releng/docs/cascading-profiles.xml
14 If you are looking for information on how to emerge something, please see
23 \fB/etc/make.profile/\fR or \fB/etc/portage/make.profile/\fR
24 site\-specific overrides go in \fB/etc/portage/profile/\fR
31 package.accept_keywords
55 package.accept_keywords
67 package-specific bashrc files
69 .BR /etc/portage/profile/
70 site-specific overrides of \fB/etc/make.profile/\fR
72 .BR /usr/portage/metadata/
77 .BR /usr/portage/profiles/
99 .BR /usr/share/portage/config/
105 misc internal cache files
108 database to track installed packages
110 .BR /var/lib/portage/
117 In the following sections, some terminology may be foreign to you or used
118 with meaning specific to Portage. Please see the referenced manpages for
119 more detailed explanations.
123 An atom is either of the form category/package or consists of an operator
124 followed by category/package followed by a hyphen and a version specification.
125 An atom might be suffixed by a slot specification.
130 .B Extended Atom Syntax
132 The following atom syntax extensions are only supported in user
133 configuration files and command line arguments for programs such as
137 .B Repository Constraints
138 Atoms with repository constraints have a '::' separator appended to the
139 right side, followed by a repository name. Each repository name should
140 correspond to the value of a \fBrepo_name\fR entry from one of the
141 repositories that is configured via the \fBPORTDIR\fR or
142 \fBPORTDIR_OVERLAY\fR variables (see \fBmake.conf\fR(5)).
146 # match sed from the 'gentoo' repository
147 sys\-apps/sed::gentoo
148 # match kdelibs from the 'kde\-testing' repository
149 kde\-base/kdelibs::kde\-testing
150 # match empathy from the 'gnome' repository
151 net\-im/empathy::gnome
155 Atoms containing wildcard patterns are of the form category/package, where
156 the special '*' wildcard character substitutes for an arbitrary number
157 of normal characters. More than one '*' character is allowed, but not two
162 # match anything from the 'sys\-apps' category
164 # match packages named 'zlib' from any category
166 # match any package from a category that begins with 'net\-'
168 # match any package name from any category
170 # match any package from the 'gentoo' repository
176 Each architecture has a unique KEYWORD.
182 A DEPEND atom that is part of the "virtual" category. They are used
183 when different packages can satisfy a dependency and only one of them is
189 .SH "SPECIFIC FILE DESCRIPTIONS"
195 The global custom settings for Portage. See \fBmake.conf\fR(5).
198 \fB/etc/make.profile/\fR or \fB/etc/portage/make.profile/\fR
199 This is usually just a symlink to the correct profile in
200 \fB/usr/portage/profiles/\fR. Since it is part of the portage tree, it
201 may easily be updated/regenerated by running `emerge \-\-sync`. It defines
202 what a profile is (usually arch specific stuff). If you need a custom
203 profile, then you should make your own \fB/etc/make.profile/\fR
204 directory and populate it. However, if you just wish to override some
205 settings, use \fB/etc/portage/profile/\fR (it supports all of the same file
206 types that \fB/etc/make.profile/\fR does, except parent). Do NOT edit the
207 settings in \fB/etc/make.profile/\fR because they WILL be lost with the next
208 `emerge \-\-sync`. If both \fB/etc/make.profile/\fR and
209 \fB/etc/portage/make.profile/\fR exist, then \fB/etc/make.profile/\fR
212 Any file in this directory, directories of other profiles or top-level
213 "profiles" directory that begins with "package." or "use." can be more than
214 just a flat file. If it is a directory, then all the files in that directory
215 will be sorted in ascending alphabetical order by file name and summed together
216 as if it were a single file. Note that this behavior is only supported since
217 portage-2.1.6.7, and it is not included in PMS at this time.
221 ${PORTDIR}/profiles/package.mask/removals
222 ${PORTDIR}/profiles/package.mask/testing
227 The existence of this file marks a profile as deprecated, meaning it is
228 not supported by Gentoo anymore. The first line must be the profile to which
229 users are encouraged to upgrade, optionally followed by some instructions
230 explaining how they can upgrade.
234 default-linux/x86/2005.0
235 # emerge -n '>=sys-apps/portage-2.0.51'
236 # rm -f /etc/make.profile
237 # ln -s /usr/portage/profiles/default-linux/alpha/2005.0 /etc/make.profile
241 The first line of this file specifies the \fBEAPI\fR to which files in the
242 same directory conform. See \fBebuild\fR(5) for information about \fBEAPI\fR
243 and related features.
246 The profile default settings for Portage. The general format is described
247 in \fBmake.conf\fR(5). The \fImake.defaults\fR for your profile defines a
248 few specific variables too:
254 Architecture type (x86/ppc/hppa/etc...).
256 .B USERLAND = \fI"GNU"\fR
257 Support BSD/cygwin/etc...
259 .B ELIBC = \fI"glibc"\fR
260 Support uClibc/BSD libc/etc...
262 .B PROFILE_ONLY_VARIABLES = \fI"ARCH"\fR
263 Prevent critical variables from being changed by the user in make.conf
267 Distinguish machines classes that have the same \fBARCH\fR. All sparc
268 machines have ARCH=sparc but set this to either 'sparc32' or 'sparc64'.
271 Special USE flags which may be needed when bootstrapping from stage1 to stage2.
276 Provides the list of packages that compose the special \fIsystem\fR set.
280 \- comments begin with # (no inline comments)
281 \- one DEPEND atom per line
282 \- packages to be added to the system set begin with a *
283 \- atoms without * only appear for legacy reasons
286 In a cascading profile setup, you can remove packages in children
287 profiles which were added by parent profiles by prefixing the atom with
293 # pull in a version of glibc less than 2.3
294 *<sys\-libs/glibc\-2.3
295 # pull in any version of bash
297 # pull in a version of readline earlier than 4.2
298 *<sys\-libs/readline\-4.2
302 A list of packages (one per line) that make up a stage1 tarball. Really only
303 useful for stage builders.
306 A list of packages (one per line) that portage should assume have been
307 provided. Useful for porting to non-Linux systems. Basically, it's a
308 list that replaces the \fBemerge \-\-inject\fR syntax.
310 For example, if you manage your own copy of a 2.6 kernel, then you can
311 tell portage that 'sys-kernel/development-sources-2.6.7' is already taken
312 care of and it should get off your back about it.
314 Portage will not attempt to update a package that is listed here unless
315 another package explicitly requires a version that is newer than what
316 has been listed. Dependencies that are satisfied by package.provided
317 entries may cause installed packages satisfying equivalent dependencies
318 to be removed by \fBemerge\fR(1) \fB\-\-depclean\fR actions (see the
319 \fBACTIONS\fR section of the \fBemerge\fR(1) man page for more information).
321 Virtual packages (virtual/*) should not be specified in package.provided.
322 Depending on the type of virtual, it may be necessary to add an entry to the
323 virtuals file and/or add a package that satisfies a virtual to
328 \- comments begin with # (no inline comments)
329 \- one DEPEND atom per line
330 \- relational operators are not allowed
331 \- must include a version
336 # you take care of the kernel
337 sys-kernel/development-sources-2.6.7
339 # you installed your own special copy of QT
342 # you have modular X but packages want monolithic
343 x11-base/xorg-x11-6.8
346 .BR package.use.force
347 Per\-package USE flag forcing.
350 In a cascading profile setup, you can remove USE flags in children
351 profiles which were added by parent profiles by prefixing the flag with
356 \- comments begin with # (no inline comments)
357 \- one DEPEND atom per line with space-delimited USE flags
362 # force docs for GTK 2.x
363 =x11\-libs/gtk+\-2* doc
364 # unforce mysql support for QT
369 Per\-package USE flag masks.
372 In a cascading profile setup, you can remove USE flags in children
373 profiles which were added by parent profiles by prefixing the flag with
378 \- comments begin with # (no inline comments)
379 \- one DEPEND atom per line with space-delimited USE flags
384 # mask docs for GTK 2.x
385 =x11\-libs/gtk+\-2* doc
386 # unmask mysql support for QT
391 This contains a path to the parent profile. It may be either relative or
392 absolute. The paths will be relative to the location of the profile. Most
393 commonly this file contains '..' to indicate the directory above. Utilized
394 only in cascading profiles.
397 If needed, this file can be used to set up a special environment for ebuilds,
398 different from the standard root environment. The syntax is the same as for
399 any other bash script.
402 Some USE flags don't make sense to disable under certain conditions. Here we
406 In a cascading profile setup, you can remove USE flags in children
407 profiles which were added by parent profiles by prefixing the flag with
412 \- comments begin with # (no inline comments)
413 \- one USE flag per line
417 Some USE flags don't make sense on some archs (for example altivec on
418 non\-ppc or mmx on non\-x86), or haven't yet been tested. Here we list
422 In a cascading profile setup, you can remove USE flags in children
423 profiles which were added by parent profiles by prefixing the flag with
428 \- comments begin with # (no inline comments)
429 \- one USE flag per line
441 This controls what packages will provide a virtual by default. For example,
442 if a package needs to send e\-mail, it will need virtual/mta. In the absence
443 of a package that provides virtual/mta (like qmail, sendmail, postfix, etc...),
444 portage will look here to see what package to use. In this case, Gentoo uses
445 net\-mail/ssmtp as the default (as defined in the virtuals file) because it's
446 the package that does the very bare minimum to send e\-mail.
450 \- comments begin with # (no inline comments)
451 \- one virtual and DEPEND atom base pair per line
456 # use net\-mail/ssmtp as the default mta
457 virtual/mta net\-mail/ssmtp
458 # use app\-dicts/aspell\-en as the default dictionary
459 virtual/aspell\-dict app\-dicts/aspell\-en
464 Any file in this directory that begins with "package." can be more than just a
465 flat file. If it is a directory, then all the files in that directory will be
466 sorted in ascending alphabetical order by file name and summed together as if
467 it were a single file.
471 /etc/portage/package.accept_keywords/common
472 /etc/portage/package.accept_keywords/e17
473 /etc/portage/package.accept_keywords/kde
478 If needed, this file can be used to set up a special environment for ebuilds,
479 different from the standard root environment. The syntax is the same as for
480 any other bash script.
482 Additional package-specific bashrc files can be created in /etc/portage/env.
485 A simple list of valid categories that may be used in /usr/portage,
486 PORTDIR_OVERLAY, and PKGDIR (see \fBmake.conf\fR(5)). This allows for custom
487 categories to be created.
491 \- one category per line
501 Contains variables customizing colors. See \fBcolor.map\fR(5).
504 The global custom settings for Portage. See \fBmake.conf\fR(5).
505 If present, this file will override settings from /etc/make.conf.
508 Whenever portage encounters a mirror:// style URI it will look up the actual
509 hosts here. If the mirror set is not found here, it will check the global
510 mirrors file at /usr/portage/profiles/thirdpartymirrors. You may also set a
511 special mirror type called "local". This list of mirrors will be checked
512 before GENTOO_MIRRORS and will be used even if the package has
513 RESTRICT="mirror" or RESTRICT="fetch".
517 \- comments begin with # (no inline comments)
518 \- mirror type followed by a list of hosts
523 # local private mirrors used only by my company
524 local ftp://192.168.0.3/mirrors/gentoo http://192.168.0.4/distfiles
526 # people in japan would want to use the japanese mirror first
527 sourceforge http://keihanna.dl.sourceforge.net/sourceforge
529 # people in tawain would want to use the local gnu mirror first
530 gnu ftp://ftp.nctu.edu.tw/UNIX/gnu/
534 This file can be used to override the metadata cache implementation. In
535 practice, portdbapi.auxdbmodule is the only variable that the user will want to
540 portdbapi.auxdbmodule = portage.cache.sqlite.database
543 After changing the portdbapi.auxdbmodule setting, it may be necessary to
544 transfer or regenerate metadata cache. Users of the rsync tree need to
545 run `emerge \-\-metadata` if they have enabled FEATURES="metadata-transfer"
546 in \fBmake.conf\fR(5). In order to regenerate metadata for repositories
547 listed in \fBPORTDIR_OVERLAY\fR or a cvs tree, run `emerge \-\-regen`
548 (see \fBemerge\fR(1)). If you use something like the sqlite module and want
549 to keep all metadata in that format alone (useful for querying), enable
550 FEATURES="metadata-transfer" in \fBmake.conf\fR(5).
552 \fBpackage.accept_keywords\fR and \fBpackage.keywords\fR
553 Per\-package ACCEPT_KEYWORDS. Useful for mixing unstable packages in with a normally
554 stable system or vice versa. This will allow ACCEPT_KEYWORDS to be augmented
555 for a single package. If both \fBpackage.accept_keywords\fR and
556 \fBpackage.keywords\fR are present, both of them will be used, and values
557 from \fBpackage.accept_keywords\fR will override values from
558 \fBpackage.keywords\fR. The \fBpackage.accept_keywords\fR file is
559 intended to replace the \fBpackage.keywords\fR file, since
560 profiles support a different form of \fBpackage.keywords\fR which
561 modifies effective KEYWORDS (rather than ACCEPT_KEYWORDS).
565 \- comment lines begin with # (no inline comments)
566 \- one DEPEND atom per line followed by additional KEYWORDS
567 \- lines without any KEYWORDS imply unstable host arch
570 # always use unstable libgd
571 media\-libs/libgd ~x86
572 # only use stable mplayer
573 media\-video/mplayer \-~x86
574 # always use unstable netcat
580 In addition to the normal values from ACCEPT_KEYWORDS package.keywords supports
581 three special tokens:
584 \fB*\fR package is visible if it is stable on any architecture
585 \fB~*\fR package is visible if it is in testing on any architecture
586 \fB**\fR package is always visible (KEYWORDS are ignored completely)
590 If you encounter the \fB-*\fR KEYWORD, this indicates that the package is known
591 to be broken on all systems which are not otherwise listed in KEYWORDS. For
592 example, a binary only package which is built for x86 will look like:
594 games-fps/quake3-demo-1.11.ebuild:KEYWORDS="-* x86"
596 If you wish to accept this package anyways, then use one of the other keywords in your
597 package.accept_keywords like this:
599 games-fps/quake3-demo x86
603 Per\-package environment variable settings. Entries refer to
604 environment files that are placed in the \fB/etc/portage/env/\fR
605 directory and have the same format as \fBmake.conf\fR(5).
609 \- comment lines begin with # (no inline comments)
610 \- one DEPEND atom per line followed by name(s) of environment file(s)
615 # use environment variables from /etc/portage/env/glibc.conf for the glibc package
616 sys\-libs/glibc glibc.conf
621 This will allow ACCEPT_LICENSE to be augmented for a single package.
625 \- comment lines begin with # (no inline comments)
626 \- one DEPEND atom per line followed by additional licenses or groups
630 A list of package atoms to mask. Useful if specific versions of packages do
631 not work well for you. For example, you swear by the Nvidia drivers, but only
632 versions earlier than 1.0.4496. No problem!
636 \- comment lines begin with # (no inline comments)
637 \- one DEPEND atom per line
642 # mask out versions 1.0.4496 of the nvidia
644 >=media\-video/nvidia\-kernel\-1.0.4496
645 >=media\-video/nvidia\-glx\-1.0.4496
648 .BR package.properties
649 This will allow ACCEPT_PROPERTIES to be augmented for a single package.
653 \- comment lines begin with # (no inline comments)
654 \- one DEPEND atom per line followed by additional properties
658 Just like package.mask above, except here you list packages you want to
659 unmask. Useful for overriding the global package.mask file (see
660 above). Note that this does not override packages that are masked via
664 Per\-package USE flags. Useful for tracking local USE flags or for
665 enabling USE flags for certain packages only. Perhaps you develop GTK
666 and thus you want documentation for it, but you don't want
667 documentation for QT. Easy as pie my friend!
671 \- comments begin with # (no inline comments)
672 \- one DEPEND atom per line with space-delimited USE flags
677 # turn on docs for GTK 2.x
678 =x11\-libs/gtk+\-2* doc
679 # disable mysql support for QT
684 Specifies \fIsite\-specific\fR repository configuration information. Note that
685 configuration settings which are specified here do not apply to tools
686 such as \fBrepoman\fR(1) and \fBegencache\fR(1), since operations
687 performed by these tools
688 are inherently \fBnot\fR \fIsite\-specific\fR. \fBWARNING:\fR Use of
689 \fBrepos.conf\fR is generally not recommended since resulting changes in
690 eclass inheritance (especially due to \fBeclass\-overrides\fR) may trigger
691 performance issues under some circumstances (see \fBbug #124041\fR). When
692 using \fBeclass\-overrides\fR, due to bug #276264, you must ensure that
693 your portage tree does not contain a metadata/cache/ directory. If that
694 directory exists then you should remove it entirely, and set
695 PORTAGE_RSYNC_EXTRA_OPTS="\-\-exclude=/metadata/cache" in
696 make.conf in order to exclude the metadata/cache/ directory during
697 \fBemerge\fR(1) \-\-sync operations.
702 # make all repositories inherit eclasses from the java\-overlay and
703 # java\-experimental repositories, with eclasses from java\-experimental
704 # taking precedence over those from java\-overlay
705 eclass\-overrides = java\-overlay java\-experimental
708 # disable all eclass overrides for ebuilds from the gentoo repository
710 # when processing metadata/layout.conf from other repositories, substitute
711 # 'gentoo' in place of references to repositories named 'foo' and 'bar'
715 # override the metadata/layout.conf masters setting from the kde-testing repo
720 .BR /etc/portage/env/
722 In this directory additional package\-specific bashrc files can be created.
723 Note that if package\-specific environment variable settings are all that's
724 needed, then \fB/etc/portage/package.env\fR should be used instead of the
725 bashrc approach that is described here.
727 set_unless_changed and unset_unless_changed functions can be used to set or
728 unset given variables only if these variable have not been set to values
729 different than values set in make.conf. This functionality can be useful for
730 temporary overriding of these variables during emerge invocation. Variables
731 set without using set_unless_changed will unconditionally override variables
732 set during emerge invocation.
736 set_unless_changed VARIABLE=VALUE
737 unset_unless_changed VALUE
740 Portage will source all of these bashrc files after \fB/etc/portage/bashrc\fR
741 in the following order:
744 /etc/portage/env/${CATEGORY}/${PN}
746 /etc/portage/env/${CATEGORY}/${PN}:${SLOT}
748 /etc/portage/env/${CATEGORY}/${P}
750 /etc/portage/env/${CATEGORY}/${PF}
753 .BR /usr/portage/metadata/
757 Specifies information about the repository layout. A
758 "masters" attribute is supported, which is used to specify names of
759 repositories which satisfy dependencies on eclasses and/or ebuilds. Each
760 repository name should correspond the value of a \fBrepo_name\fR entry
761 from one of the repositories that is configured via the \fBPORTDIR\fR or
762 \fBPORTDIR_OVERLAY\fR variables (see \fBmake.conf\fR(5)). Repositories listed
763 toward the right of the \fBmasters\fR list take precedence over those listed
764 toward the left of the list. An "aliases" attribute is also supported, which
765 behaves like an "aliases" attribute in \fBrepos.conf\fR. \fISite-specific\fR
766 overrides to \fBlayout.conf\fR settings may be specified in
767 \fB/etc/portage/repos.conf\fR. Settings in \fBrepos.conf\fR take
768 precedence over settings in \fBlayout.conf\fR, except tools such as
769 \fBrepoman\fR(1) and \fBegencache\fR(1) will entirely ignore
770 \fBrepos.conf\fR since their operations are inherently \fBnot\fR
771 \fIsite\-specific\fR.
775 # eclasses provided by java-overlay take precedence over identically named
776 # eclasses that are provided by gentoo
777 masters = gentoo java-overlay
778 # indicate that this repo can be used as a substitute for foo-overlay
779 aliases = foo-overlay
780 # do not sign manifests in this repo
781 sign\-manifests = false
782 # thin\-manifests only contain DIST entries
783 thin\-manifests = true
784 # indicate that this repo requires manifests for each package, and is
785 # considered a failure if a manifest file is missing/incorrect
786 use\-manifests = strict
790 .BR /usr/portage/profiles/
791 Global Gentoo settings that are controlled by the developers. To override
792 these settings, you can use the files in \fB/etc/portage/\fR.
796 A list of all valid KEYWORDS. This does not include modifiers.
800 \- one KEYWORD per line
811 A simple list of valid categories that may be used in /usr/portage,
812 PORTDIR_OVERLAY, and PKGDIR (see \fBmake.conf\fR(5)).
816 \- one category per line
828 A list of all the packages which will be displayed when you run `emerge info`.
831 A list of all the variables which will be displayed when you run `emerge info`.
834 This contains groups of licenses that may be specifed in the
835 \fBACCEPT_LICENSE\fR variable (see \fBmake.conf\fR(5)). Refer
836 to GLEP 23 for further information:
837 \fIhttp://www.gentoo.org/proj/en/glep/glep-0023.html\fR.
841 \- comments begin with # (no inline comments)
842 \- one group name, followed by list of licenses and nested groups
843 \- nested groups are prefixed with the '@' symbol
848 # The FSF-APPROVED group includes the entire GPL-COMPATIBLE group and more.
849 FSF-APPROVED @GPL-COMPATIBLE Apache-1.1 BSD-4 MPL-1.0 MPL-1.1
850 # The GPL-COMPATIBLE group includes all licenses compatible with the GNU GPL.
851 GPL-COMPATIBLE Apache-2.0 BSD BSD-2 GPL-2 GPL-3 LGPL-2.1 LGPL-3 X11 ZLIB
854 .BR package.accept_keywords
855 Per\-package ACCEPT_KEYWORDS for profiles. This has the same format and
856 behavior as /etc/portage/package.accept_keywords, including the ability
857 to list atoms without any keywords in order to accept unstable variants
858 of all stable keywords listed in ACCEPT_KEYWORDS.
861 Per\-profile KEYWORDS. Useful for cases in which the effective KEYWORDS of a
862 given package should vary depending on which profile the user has selected.
866 \- comment lines begin with # (no inline comments)
867 \- one DEPEND atom per line followed by additional KEYWORDS
872 # add stable keyword to libgd
873 media\-libs/libgd x86
874 # remove stable keyword from mplayer and add unstable keyword
875 media\-video/mplayer \-x86 ~x86
876 # remove all keywords from netcat
877 net-analyzer/netcat -*
881 This contains a list of DEPEND atoms for packages that should not be installed
882 in any profile. Useful for adding the latest KDE betas and making sure no
883 one accidentally upgrades to them. Also useful for quickly masking specific
884 versions due to security issues. ALWAYS include a comment explaining WHY the
885 package has been masked and WHO is doing the masking.
889 \- comments begin with # (no inline comments)
890 \- one DEPEND atom per line
895 # masked for security reasons
896 <sys\-libs/zlib\-1.1.4
897 # <caleb@gentoo.org> (10 Sep 2003)
899 =kde\-base/kde\-3.2.0_beta1
900 =kde\-base/kdeaccessibility\-3.2.0_beta1
904 List all the current stable and development profiles. If a profile is listed
905 here, then it will be checked by repoman.
908 \- comments begin with # (no inline comments)
909 \- one profile list per line in format: arch dir status
910 \- arch must be listed in arch.list
911 \- dir is relative to profiles.desc
912 \- status must be 'stable', 'dev', or 'exp'
917 alpha default/linux/alpha/10.0 stable
918 m68k default/linux/m68k/10.0 dev
919 x86 default/linux/x86/10.0 stable
920 x86-linux prefix/linux/x86 exp
924 The first line of the file should define a unique repository name. The name
925 may contain any of the characters [A\-Za\-z0\-9_\-]. It must not begin with a
928 .BR thirdpartymirrors
929 Controls the mapping of mirror:// style URIs to actual lists of
930 mirrors. Keeps us from overloading a single server.
934 \- comments begin with # (no inline comments)
935 \- mirror type followed by a list of hosts
940 sourceforge http://aleron.dl.sourceforge.net/sourceforge http://unc.dl.sourceforge.net/sourceforge
942 gentoo http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo/distfiles
944 kernel http://www.kernel.org/pub http://www.us.kernel.org/pub
948 All global USE flags must be listed here with a description of what they do.
952 \- comments begin with # (no inline comments)
953 \- use flag \- some description
958 3dfx \- Adds support for 3dfx video cards
959 acl \- Adds support for Access Control Lists
960 doc \- Adds extra documentation
964 All local USE flags are listed here along with the package and a
965 description. This file is automatically generated from the
966 metadata.xml files that are included with each individual package.
967 Refer to GLEP 56 for further information:
968 \fIhttp://www.gentoo.org/proj/en/glep/glep-0056.html\fR.
972 \- comments begin with # (no inline comments)
973 \- package:use flag \- description
976 app\-editors/nano:justify \- Toggles the justify option
977 dev\-libs/DirectFB:fusion \- Adds Multi Application support
978 games\-emulation/xmess:net \- Adds network support
982 .BR /usr/share/portage/config/
986 The global default settings for Portage. This comes from the portage package
987 itself. Settings in \fBmake.conf\fR or \fBpackage.env\fR
988 override values here. The format
989 is described extensivly in \fBmake.conf\fR(5).
994 This directory is used to store internal portage cache files. The names and
995 purpose of these files are not documented on purpose so as to keep down bitrot
996 as internals change. If you aren't working on portage internally, then the
997 details most likely do not matter to you.
999 This entire directory can be safely deleted. It is highly recommended you do
1000 not do this however as it can be a time consuming process to generate them all
1006 All installed package information is recorded here. If portage thinks you have
1007 a package installed, it is usually because it is listed here.
1009 The format follows somewhat closely that of the portage tree. There is a
1010 directory for each category and a package-version subdirectory for each package
1013 Inside each package directory are misc files that describe the installed
1014 contents of the package as well as build time information (so that the package
1015 can be unmerged without needing the portage tree).
1017 The exact file contents and format are not described here again so that things
1018 can be changed quickly. Generally though there is one file per environment
1019 variable that "matters" (like CFLAGS) with the contents stored inside of it.
1020 Another common file is the CONTENTS file which lists the path and hashes of
1021 all objects that the package installed onto your system.
1024 .BR /var/lib/portage/
1028 Hashes which are used to determine whether files in config protected
1029 directories have been modified since being installed. Files which have not
1030 been modified will automatically be unmerged.
1033 Every time you emerge a package, the package that you requested is
1034 recorded here. Then when you run `emerge world \-up`, the list of
1035 packages is read from this file. Note that this does not mean that the
1036 packages that were installed as dependencies are listed here. For
1037 example, if you run `emerge mod_wsgi` and you do not have apache
1038 already, then "www\-apache/mod_wsgi" is recorded in the world file but
1039 "www\-servers/apache" is not. For more information, review \fBemerge\fR(1).
1043 \- one DEPEND atom base per line
1048 games\-misc/fortune\-mod\-gentoo\-dev
1054 This is like the world file but instead of package atoms it contains
1055 packages sets which always begin with the @ character.
1062 .SH "REPORTING BUGS"
1063 Please report bugs via http://bugs.gentoo.org/
1066 Marius Mauch <genone@gentoo.org>
1067 Mike Frysinger <vapier@gentoo.org>
1068 Drake Wyrm <wyrm@haell.com>
1069 Arfrever Frehtes Taifersar Arahesis <arfrever@gentoo.org>