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/
92 .BR /usr/share/portage/config/
98 misc internal cache files
101 database to track installed packages
103 .BR /var/lib/portage/
110 In the following sections, some terminology may be foreign to you or used
111 with meaning specific to Portage. Please see the referenced manpages for
112 more detailed explanations.
116 An atom is either of the form category/package or consists of an operator
117 followed by category/package followed by a hyphen and a version specification.
118 An atom might be prefixed by a slot specification.
119 The extended atom syntax allows atoms of the form category/package, where an
120 arbitrary number of characters has been replaced by a '*'. An extended atom may contain
121 more than one '*', but not two next to each other. The extend atom syntax is only
122 available in user configuration files and for some command line options.
128 Each architecture has a unique KEYWORD.
134 A DEPEND atom that is part of the "virtual" category. They are used
135 when different packages can satisfy a dependency and only one of them is
141 .SH "SPECIFIC FILE DESCRIPTIONS"
147 The global custom settings for Portage. See \fBmake.conf\fR(5).
150 \fB/etc/make.profile/\fR or \fB/etc/portage/make.profile/\fR
151 This is usually just a symlink to the correct profile in
152 \fB/usr/portage/profiles/\fR. Since it is part of the portage tree, it
153 may easily be updated/regenerated by running `emerge \-\-sync`. It defines
154 what a profile is (usually arch specific stuff). If you need a custom
155 profile, then you should make your own \fB/etc/make.profile/\fR
156 directory and populate it. However, if you just wish to override some
157 settings, use \fB/etc/portage/profile/\fR (it supports all of the same file
158 types that \fB/etc/make.profile/\fR does, except parent). Do NOT edit the
159 settings in \fB/etc/make.profile/\fR because they WILL be lost with the next
160 `emerge \-\-sync`. If both \fB/etc/make.profile/\fR and
161 \fB/etc/portage/make.profile/\fR exist, then \fB/etc/make.profile/\fR
164 Any file in this directory, directories of other profiles or top-level
165 "profiles" directory that begins with "package." or "use." can be more than
166 just a flat file. If it is a directory, then all the files in that directory
167 will be sorted in ascending alphabetical order by file name and summed together
168 as if it were a single file. Note that this behavior is only supported since
169 portage-2.1.6.7, and it is not included in PMS at this time.
173 ${PORTDIR}/profiles/package.mask/removals
174 ${PORTDIR}/profiles/package.mask/testing
179 The existence of this file marks a profile as deprecated, meaning it is
180 not supported by Gentoo anymore. The first line must be the profile to which
181 users are encouraged to upgrade, optionally followed by some instructions
182 explaining how they can upgrade.
186 default-linux/x86/2005.0
187 # emerge -n '>=sys-apps/portage-2.0.51'
188 # rm -f /etc/make.profile
189 # ln -s /usr/portage/profiles/default-linux/alpha/2005.0 /etc/make.profile
193 The first line of this file specifies the \fBEAPI\fR to which files in the
194 same directory conform. See \fBebuild\fR(5) for information about \fBEAPI\fR
195 and related features.
198 The profile default settings for Portage. The general format is described
199 in \fBmake.conf\fR(5). The \fImake.defaults\fR for your profile defines a
200 few specific variables too:
206 Architecture type (x86/ppc/hppa/etc...).
208 .B USERLAND = \fI"GNU"\fR
209 Support BSD/cygwin/etc...
211 .B ELIBC = \fI"glibc"\fR
212 Support uClibc/BSD libc/etc...
214 .B PROFILE_ONLY_VARIABLES = \fI"ARCH"\fR
215 Prevent critical variables from being changed by the user in make.conf
219 Distinguish machines classes that have the same \fBARCH\fR. All sparc
220 machines have ARCH=sparc but set this to either 'sparc32' or 'sparc64'.
223 Special USE flags which may be needed when bootstrapping from stage1 to stage2.
228 Provides the list of packages that compose the special \fIsystem\fR set.
232 \- comments begin with # (no inline comments)
233 \- one DEPEND atom per line
234 \- packages to be added to the system set begin with a *
237 In a cascading profile setup, you can remove packages in children
238 profiles which were added by parent profiles by prefixing the atom with
244 # pull in a version of glibc less than 2.3
245 *<sys\-libs/glibc\-2.3
246 # pull in any version of bash
248 # pull in a version of readline earlier than 4.2
249 *<sys\-libs/readline\-4.2
253 A list of packages (one per line) that make up a stage1 tarball. Really only
254 useful for stage builders.
257 A list of packages (one per line) that portage should assume have been
258 provided. Useful for porting to non-Linux systems. Basically, it's a
259 list that replaces the \fBemerge \-\-inject\fR syntax.
261 For example, if you manage your own copy of a 2.6 kernel, then you can
262 tell portage that 'sys-kernel/development-sources-2.6.7' is already taken
263 care of and it should get off your back about it.
265 Portage will not attempt to update a package that is listed here unless
266 another package explicitly requires a version that is newer than what
267 has been listed. Dependencies that are satisfied by package.provided
268 entries may cause installed packages satisfying equivalent dependencies
269 to be removed by \fBemerge\fR(1) \fB\-\-depclean\fR actions (see the
270 \fBACTIONS\fR section of the \fBemerge\fR(1) man page for more information).
272 Virtual packages (virtual/*) should not be specified in package.provided.
273 Depending on the type of virtual, it may be necessary to add an entry to the
274 virtuals file and/or add a package that satisfies a virtual to
279 \- comments begin with # (no inline comments)
280 \- one DEPEND atom per line
281 \- relational operators are not allowed
282 \- must include a version
287 # you take care of the kernel
288 sys-kernel/development-sources-2.6.7
290 # you installed your own special copy of QT
293 # you have modular X but packages want monolithic
294 x11-base/xorg-x11-6.8
297 .BR package.use.force
298 Per\-package USE flag forcing.
301 In a cascading profile setup, you can remove USE flags in children
302 profiles which were added by parent profiles by prefixing the flag with
307 \- comments begin with # (no inline comments)
308 \- one DEPEND atom per line with space-delimited USE flags
313 # force docs for GTK 2.x
314 =x11\-libs/gtk+\-2* doc
315 # unforce mysql support for QT
320 Per\-package USE flag masks.
323 In a cascading profile setup, you can remove USE flags in children
324 profiles which were added by parent profiles by prefixing the flag with
329 \- comments begin with # (no inline comments)
330 \- one DEPEND atom per line with space-delimited USE flags
335 # mask docs for GTK 2.x
336 =x11\-libs/gtk+\-2* doc
337 # unmask mysql support for QT
342 This contains a path to the parent profile. It may be either relative or
343 absolute. The paths will be relative to the location of the profile. Most
344 commonly this file contains '..' to indicate the directory above. Utilized
345 only in cascading profiles.
348 If needed, this file can be used to set up a special environment for ebuilds,
349 different from the standard root environment. The syntax is the same as for
350 any other bash script.
353 Some USE flags don't make sense to disable under certain conditions. Here we
357 In a cascading profile setup, you can remove USE flags in children
358 profiles which were added by parent profiles by prefixing the flag with
363 \- comments begin with # (no inline comments)
364 \- one USE flag per line
368 Some USE flags don't make sense on some archs (for example altivec on
369 non\-ppc or mmx on non\-x86), or haven't yet been tested. Here we list
373 In a cascading profile setup, you can remove USE flags in children
374 profiles which were added by parent profiles by prefixing the flag with
379 \- comments begin with # (no inline comments)
380 \- one USE flag per line
392 This controls what packages will provide a virtual by default. For example,
393 if a package needs to send e\-mail, it will need virtual/mta. In the absence
394 of a package that provides virtual/mta (like qmail, sendmail, postfix, etc...),
395 portage will look here to see what package to use. In this case, Gentoo uses
396 net\-mail/ssmtp as the default (as defined in the virtuals file) because it's
397 the package that does the very bare minimum to send e\-mail.
401 \- comments begin with # (no inline comments)
402 \- one virtual and DEPEND atom base pair per line
407 # use net\-mail/ssmtp as the default mta
408 virtual/mta net\-mail/ssmtp
409 # use app\-dicts/aspell\-en as the default dictionary
410 virtual/aspell\-dict app\-dicts/aspell\-en
415 Any file in this directory that begins with "package." can be more than just a
416 flat file. If it is a directory, then all the files in that directory will be
417 sorted in ascending alphabetical order by file name and summed together as if
418 it were a single file.
422 /etc/portage/package.accept_keywords/common
423 /etc/portage/package.accept_keywords/e17
424 /etc/portage/package.accept_keywords/kde
429 If needed, this file can be used to set up a special environment for ebuilds,
430 different from the standard root environment. The syntax is the same as for
431 any other bash script.
433 Additional package-specific bashrc files can be created in /etc/portage/env.
436 A simple list of valid categories that may be used in /usr/portage,
437 PORTDIR_OVERLAY, and PKGDIR (see \fBmake.conf\fR(5)). This allows for custom
438 categories to be created.
442 \- one category per line
452 Contains variables customizing colors. See \fBcolor.map\fR(5).
455 The global custom settings for Portage. See \fBmake.conf\fR(5).
456 If present, this file will override settings from /etc/make.conf.
459 Whenever portage encounters a mirror:// style URI it will look up the actual
460 hosts here. If the mirror set is not found here, it will check the global
461 mirrors file at /usr/portage/profiles/thirdpartymirrors. You may also set a
462 special mirror type called "local". This list of mirrors will be checked
463 before GENTOO_MIRRORS and will be used even if the package has
464 RESTRICT="mirror" or RESTRICT="fetch".
468 \- comments begin with # (no inline comments)
469 \- mirror type followed by a list of hosts
474 # local private mirrors used only by my company
475 local ftp://192.168.0.3/mirrors/gentoo http://192.168.0.4/distfiles
477 # people in japan would want to use the japanese mirror first
478 sourceforge http://keihanna.dl.sourceforge.net/sourceforge
480 # people in tawain would want to use the local gnu mirror first
481 gnu ftp://ftp.nctu.edu.tw/UNIX/gnu/
485 This file can be used to override the metadata cache implementation. In
486 practice, portdbapi.auxdbmodule is the only variable that the user will want to
491 portdbapi.auxdbmodule = portage.cache.sqlite.database
494 After changing the portdbapi.auxdbmodule setting, it may be necessary to
495 transfer or regenerate metadata cache. Users of the rsync tree need to
496 run `emerge \-\-metadata` if they have enabled FEATURES="metadata-transfer"
497 in \fBmake.conf\fR(5). In order to regenerate metadata for repositories
498 listed in \fBPORTDIR_OVERLAY\fR or a cvs tree, run `emerge \-\-regen`
499 (see \fBemerge\fR(1)). If you use something like the sqlite module and want
500 to keep all metadata in that format alone (useful for querying), enable
501 FEATURES="metadata-transfer" in \fBmake.conf\fR(5).
503 \fBpackage.accept_keywords\fR and \fBpackage.keywords\fR
504 Per\-package ACCEPT_KEYWORDS. Useful for mixing unstable packages in with a normally
505 stable system or vice versa. This will allow ACCEPT_KEYWORDS to be augmented
506 for a single package. If both \fBpackage.accept_keywords\fR and
507 \fBpackage.keywords\fR are present, both of them will be used, and values
508 from \fBpackage.accept_keywords\fR will override values from
509 \fBpackage.keywords\fR. The \fBpackage.accept_keywords\fR file is
510 intended to replace the \fBpackage.keywords\fR file, since
511 profiles support a different form of \fBpackage.keywords\fR which
512 modifies effective KEYWORDS (rather than ACCEPT_KEYWORDS).
516 \- comment lines begin with # (no inline comments)
517 \- one DEPEND atom per line followed by additional KEYWORDS
518 \- lines without any KEYWORDS imply unstable host arch
521 # always use unstable libgd
522 media\-libs/libgd ~x86
523 # only use stable mplayer
524 media\-video/mplayer \-~x86
525 # always use unstable netcat
531 In addition to the normal values from ACCEPT_KEYWORDS package.keywords supports
532 three special tokens:
535 \fB*\fR package is visible if it is stable on any architecture
536 \fB~*\fR package is visible if it is in testing on any architecture
537 \fB**\fR package is always visible (KEYWORDS are ignored completely)
541 If you encounter the \fB-*\fR KEYWORD, this indicates that the package is known
542 to be broken on all systems which are not otherwise listed in KEYWORDS. For
543 example, a binary only package which is built for x86 will look like:
545 games-fps/quake3-demo-1.11.ebuild:KEYWORDS="-* x86"
547 If you wish to accept this package anyways, then use one of the other keywords in your
548 package.accept_keywords like this:
550 games-fps/quake3-demo x86
554 Per\-package environment variable settings. Entries refer to
555 environment files that are placed in the \fB/etc/portage/env/\fR
556 directory and have the same format as \fBmake.conf\fR(5).
560 \- comment lines begin with # (no inline comments)
561 \- one DEPEND atom per line followed by name(s) of environment file(s)
566 # use environment variables from /etc/portage/env/glibc.conf for the glibc package
567 sys\-libs/glibc glibc.conf
572 This will allow ACCEPT_LICENSE to be augmented for a single package.
576 \- comment lines begin with # (no inline comments)
577 \- one DEPEND atom per line followed by additional licenses or groups
581 A list of package atoms to mask. Useful if specific versions of packages do
582 not work well for you. For example, you swear by the Nvidia drivers, but only
583 versions earlier than 1.0.4496. No problem!
587 \- comment lines begin with # (no inline comments)
588 \- one DEPEND atom per line
593 # mask out versions 1.0.4496 of the nvidia
595 >=media\-video/nvidia\-kernel\-1.0.4496
596 >=media\-video/nvidia\-glx\-1.0.4496
599 .BR package.properties
600 This will allow ACCEPT_PROPERTIES to be augmented for a single package.
604 \- comment lines begin with # (no inline comments)
605 \- one DEPEND atom per line followed by additional properties
609 Just like package.mask above, except here you list packages you want to
610 unmask. Useful for overriding the global package.mask file (see
611 above). Note that this does not override packages that are masked via
615 Per\-package USE flags. Useful for tracking local USE flags or for
616 enabling USE flags for certain packages only. Perhaps you develop GTK
617 and thus you want documentation for it, but you don't want
618 documentation for QT. Easy as pie my friend!
622 \- comments begin with # (no inline comments)
623 \- one DEPEND atom per line with space-delimited USE flags
628 # turn on docs for GTK 2.x
629 =x11\-libs/gtk+\-2* doc
630 # disable mysql support for QT
635 Specifies \fIsite\-specific\fR repository configuration information. Note that
636 configuration settings which are specified here do not apply to tools
637 such as \fBrepoman\fR(1) and \fBegencache\fR(1), since operations
638 performed by these tools
639 are inherently \fBnot\fR \fIsite\-specific\fR. \fBWARNING:\fR Use of
640 \fBrepos.conf\fR is generally not recommended since resulting changes in
641 eclass inheritance (especially due to \fBeclass\-overrides\fR) may trigger
642 performance issues under some circumstances (see \fBbug #124041\fR). When
643 using \fBeclass\-overrides\fR, due to bug #276264, you must ensure that
644 your portage tree does not contain a metadata/cache/ directory. If that
645 directory exists then you should remove it entirely, and set
646 PORTAGE_RSYNC_EXTRA_OPTS="\-\-exclude=/metadata/cache" in
647 make.conf in order to exclude the metadata/cache/ directory during
648 \fBemerge\fR(1) \-\-sync operations.
653 # make all repositories inherit eclasses from the java\-overlay and
654 # java\-experimental repositories, with eclasses from java\-experimental
655 # taking precedence over those from java\-overlay
656 eclass\-overrides = java\-overlay java\-experimental
659 # disable all eclass overrides for ebuilds from the gentoo repository
661 # when processing metadata/layout.conf from other repositories, substitute
662 # 'gentoo' in place of references to repositories named 'foo' and 'bar'
666 # override the metadata/layout.conf masters setting from the kde-testing repo
671 .BR /etc/portage/env/
673 In this directory additional package\-specific bashrc files can be created.
674 Note that if package\-specific environment variable settings are all that's
675 needed, then \fB/etc/portage/package.env\fR should be used instead of the
676 bashrc approach that is described here.
678 set_unless_changed and unset_unless_changed functions can be used to set or
679 unset given variables only if these variable have not been set to values
680 different than values set in make.conf. This functionality can be useful for
681 temporary overriding of these variables during emerge invocation. Variables
682 set in the usual VARIABLE=VALUE style will unconditionally override variables
683 set during emerge invocation.
687 set_unless_changed VARIABLE VALUE
688 unset_unless_changed VALUE
691 Portage will source all of these bashrc files after \fB/etc/portage/bashrc\fR
692 in the following order:
695 /etc/portage/env/${CATEGORY}/${PN}
697 /etc/portage/env/${CATEGORY}/${PN}:${SLOT}
699 /etc/portage/env/${CATEGORY}/${P}
701 /etc/portage/env/${CATEGORY}/${PF}
704 .BR /usr/portage/metadata/
708 Specifies information about the repository layout. A
709 "masters" attribute is supported, which is used to specify names of
710 repositories which satisfy dependencies on eclasses and/or ebuilds. Each
711 repository name should correspond the value of a \fBrepo_name\fR entry
712 from one of the repositories that is configured via the \fBPORTDIR\fR or
713 \fBPORTDIR_OVERLAY\fR variables (see \fBmake.conf\fR(5)). Repositories listed
714 toward the right of the \fBmasters\fR list take precedence over those listed
715 toward the left of the list. An "aliases" attribute is also supported, which
716 behaves like an "aliases" attribute in \fBrepos.conf\fR. \fISite-specific\fR
717 overrides to \fBlayout.conf\fR settings may be specified in
718 \fB/etc/portage/repos.conf\fR. Settings in \fBrepos.conf\fR take
719 precedence over settings in \fBlayout.conf\fR, except tools such as
720 \fBrepoman\fR(1) and \fBegencache\fR(1) will entirely ignore
721 \fBrepos.conf\fR since their operations are inherently \fBnot\fR
722 \fIsite\-specific\fR.
726 # eclasses provided by java-overlay take precedence over identically named
727 # eclasses that are provided by gentoo
728 masters = gentoo java-overlay
729 # indicate that this repo can be used as a substitute for foo-overlay
730 aliases = foo-overlay
734 .BR /usr/portage/profiles/
735 Global Gentoo settings that are controlled by the developers. To override
736 these settings, you can use the files in \fB/etc/portage/\fR.
740 A list of all valid KEYWORDS. This does not include modifiers.
744 \- one KEYWORD per line
755 A simple list of valid categories that may be used in /usr/portage,
756 PORTDIR_OVERLAY, and PKGDIR (see \fBmake.conf\fR(5)).
760 \- one category per line
772 A list of all the packages which will be displayed when you run `emerge info`.
775 A list of all the variables which will be displayed when you run `emerge info`.
778 This contains groups of licenses that may be specifed in the
779 \fBACCEPT_LICENSE\fR variable (see \fBmake.conf\fR(5)). Refer
780 to GLEP 23 for further information:
781 \fIhttp://www.gentoo.org/proj/en/glep/glep-0023.html\fR.
785 \- comments begin with # (no inline comments)
786 \- one group name, followed by list of licenses and nested groups
787 \- nested groups are prefixed with the '@' symbol
792 # The FSF-APPROVED group includes the entire GPL-COMPATIBLE group and more.
793 FSF-APPROVED @GPL-COMPATIBLE Apache-1.1 BSD-4 MPL-1.0 MPL-1.1
794 # The GPL-COMPATIBLE group includes all licenses compatible with the GNU GPL.
795 GPL-COMPATIBLE Apache-2.0 BSD BSD-2 GPL-2 GPL-3 LGPL-2.1 LGPL-3 X11 ZLIB
798 .BR package.accept_keywords
799 Per\-package ACCEPT_KEYWORDS for profiles. This has the same format and
800 behavior as /etc/portage/package.accept_keywords, including the ability
801 to list atoms without any keywords in order to accept unstable variants
802 of all stable keywords listed in ACCEPT_KEYWORDS.
805 Per\-profile KEYWORDS. Useful for cases in which the effective KEYWORDS of a
806 given package should vary depending on which profile the user has selected.
810 \- comment lines begin with # (no inline comments)
811 \- one DEPEND atom per line followed by additional KEYWORDS
816 # add stable keyword to libgd
817 media\-libs/libgd x86
818 # remove stable keyword from mplayer and add unstable keyword
819 media\-video/mplayer \-x86 ~x86
820 # remove all keywords from netcat
821 net-analyzer/netcat -*
825 This contains a list of DEPEND atoms for packages that should not be installed
826 in any profile. Useful for adding the latest KDE betas and making sure no
827 one accidentally upgrades to them. Also useful for quickly masking specific
828 versions due to security issues. ALWAYS include a comment explaining WHY the
829 package has been masked and WHO is doing the masking.
833 \- comments begin with # (no inline comments)
834 \- one DEPEND atom per line
839 # masked for security reasons
840 <sys\-libs/zlib\-1.1.4
841 # <caleb@gentoo.org> (10 Sep 2003)
843 =kde\-base/kde\-3.2.0_beta1
844 =kde\-base/kdeaccessibility\-3.2.0_beta1
848 List all the current stable and development profiles. If a profile is listed
849 here, then it will be checked by repoman.
852 \- comments begin with # (no inline comments)
853 \- one profile list per line in format: arch dir status
854 \- arch must be listed in arch.list
855 \- dir is relative to profiles.desc
856 \- status must be 'stable', 'dev', or 'exp'
861 alpha default/linux/alpha/10.0 stable
862 m68k default/linux/m68k/10.0 dev
863 x86 default/linux/x86/10.0 stable
864 x86-linux prefix/linux/x86 exp
868 The first line of the file should define a unique repository name. The name
869 may contain any of the characters [A\-Za\-z0\-9_\-]. It must not begin with a
872 .BR thirdpartymirrors
873 Controls the mapping of mirror:// style URIs to actual lists of
874 mirrors. Keeps us from overloading a single server.
878 \- comments begin with # (no inline comments)
879 \- mirror type followed by a list of hosts
884 sourceforge http://aleron.dl.sourceforge.net/sourceforge http://unc.dl.sourceforge.net/sourceforge
886 gentoo http://distro.ibiblio.org/pub/linux/distributions/gentoo/distfiles/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo/distfiles
888 kernel http://www.kernel.org/pub http://www.us.kernel.org/pub
892 All global USE flags must be listed here with a description of what they do.
896 \- comments begin with # (no inline comments)
897 \- use flag \- some description
902 3dfx \- Adds support for 3dfx video cards
903 acl \- Adds support for Access Control Lists
904 doc \- Adds extra documentation
908 All local USE flags are listed here along with the package and a
909 description. This file is automatically generated from the
910 metadata.xml files that are included with each individual package.
911 Refer to GLEP 56 for further information:
912 \fIhttp://www.gentoo.org/proj/en/glep/glep-0056.html\fR.
916 \- comments begin with # (no inline comments)
917 \- package:use flag \- description
920 app\-editors/nano:justify \- Toggles the justify option
921 dev\-libs/DirectFB:fusion \- Adds Multi Application support
922 games\-emulation/xmess:net \- Adds network support
926 .BR /usr/share/portage/config/
930 The global default settings for Portage. This comes from the portage package
931 itself. Settings in \fBmake.conf\fR or \fBpackage.env\fR
932 override values here. The format
933 is described extensivly in \fBmake.conf\fR(5).
938 This directory is used to store internal portage cache files. The names and
939 purpose of these files are not documented on purpose so as to keep down bitrot
940 as internals change. If you aren't working on portage internally, then the
941 details most likely do not matter to you.
943 This entire directory can be safely deleted. It is highly recommended you do
944 not do this however as it can be a time consuming process to generate them all
950 All installed package information is recorded here. If portage thinks you have
951 a package installed, it is usually because it is listed here.
953 The format follows somewhat closely that of the portage tree. There is a
954 directory for each category and a package-version subdirectory for each package
957 Inside each package directory are misc files that describe the installed
958 contents of the package as well as build time information (so that the package
959 can be unmerged without needing the portage tree).
961 The exact file contents and format are not described here again so that things
962 can be changed quickly. Generally though there is one file per environment
963 variable that "matters" (like CFLAGS) with the contents stored inside of it.
964 Another common file is the CONTENTS file which lists the path and hashes of
965 all objects that the package installed onto your system.
968 .BR /var/lib/portage/
972 Hashes which are used to determine whether files in config protected
973 directories have been modified since being installed. Files which have not
974 been modified will automatically be unmerged.
977 Every time you emerge a package, the package that you requested is
978 recorded here. Then when you run `emerge world \-up`, the list of
979 packages is read from this file. Note that this does not mean that the
980 packages that were installed as dependencies are listed here. For
981 example, if you run `emerge mod_wsgi` and you do not have apache
982 already, then "www\-apache/mod_wsgi" is recorded in the world file but
983 "www\-servers/apache" is not. For more information, review \fBemerge\fR(1).
987 \- one DEPEND atom base per line
992 games\-misc/fortune\-mod\-gentoo\-dev
998 This is like the world file but instead of package atoms it contains
999 packages sets which always begin with the @ character.
1006 .SH "REPORTING BUGS"
1007 Please report bugs via http://bugs.gentoo.org/
1010 Marius Mauch <genone@gentoo.org>
1011 Mike Frysinger <vapier@gentoo.org>
1012 Drake Wyrm <wyrm@haell.com>
1013 Arfrever Frehtes Taifersar Arahesis <arfrever@gentoo.org>