-.TH "PORTAGE" "5" "Jun 2007" "Portage 2.1.3" "Portage"
+.TH "PORTAGE" "5" "Dec 2005" "Portage 2.1" "Portage"
.SH NAME
portage \- the heart of Gentoo
.SH "DESCRIPTION"
.fi
.TP
.BR /etc/make.profile/
-site\-specific overrides go in \fB/etc/portage/profile/\fR
.nf
deprecated
make.defaults
packages
packages.build
-package.mask
package.provided
package.use
package.use.force
.BR /etc/portage/
.nf
bashrc
-color.map
modules
package.keywords
package.mask
what a profile is (usually arch specific stuff). If you need a custom
profile, then you should make your own \fB/etc/make.profile/\fR
directory and populate it. However, if you just wish to override some
-settings, use \fB/etc/portage/profile/\fR (it supports all of the same file
-types that \fB/etc/make.profile/\fR does, except parent). Do NOT edit the
-settings in \fB/etc/make.profile/\fR because they WILL be lost with the next
-`emerge \-\-sync`.
+settings, do NOT edit these files because they WILL be lost with the
+next `emerge \-\-sync`. See the section below on \fB/etc/portage/\fR for
+overriding.
.RS
.TP
.BR deprecated
different from the standard root environment. The syntax is the same as for
any other bash script.
.TP
-.BR color.map
-Contains variables customizing colors. See \fBcolor.map\fR(5).
-.TP
.BR modules
This file can be used to override the metadata cache implementation. In
practice, portdbapi.auxdbmodule is the only variable that the user will want to
.BR emerge (1),
.BR ebuild (1),
.BR ebuild (5),
-.BR make.conf (5),
-.BR color.map (5)
+.BR make.conf (5)