For bug #186639, note that /etc/portage/profile/ supports all of the same file types...

svn path=/main/branches/2.1.2.9/; revision=7509

diff --git a/man/portage.5 b/man/portage.5
index dc72d546720ce7a81fed8541d5bc69163db8c847..cc0110a23e2e2435acc122f9c477eb2bf62b63e9 100644 (file)
--- a/man/portage.5
+++ b/man/portage.5
@@ -22,11 +22,13 @@ make.globals
 .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
@@ -126,9 +128,10 @@ may easily be updated/regenerated by running `emerge \-\-sync`.  It defines
 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, 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.
+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`.
 .RS
 .TP
 .BR deprecated