Add a note that PORTDIR is a repository of software and that users

should not add random directories in it. (trunk r9209)

svn path=/main/branches/2.1.2/; revision=9243

diff --git a/man/make.conf.5 b/man/make.conf.5
index 220d045d75a046bc327a34da90fa8599a6176496..072f24e8e06ac288f2403e52ba6cbfbbc83f1d8d 100644 (file)
--- a/man/make.conf.5
+++ b/man/make.conf.5
@@ -440,7 +440,9 @@ Data stored inside \fBPORTDIR\fR is in peril of being overwritten or deleted by
 the emerge \-\-sync command. The default value of
 \fBPORTAGE_RSYNC_OPTS\fR will protect the default locations of
 \fBDISTDIR\fR and \fBPKGDIR\fR, but users are warned that any other locations
-inside \fBPORTDIR\fR are not necessarily safe for data storage.
+inside \fBPORTDIR\fR are not necessarily safe for data storage.  You should not 
+put other data (such as overlays) in your \fBPORTDIR\fB.  Portage will walk 
+directory structures and may arbitrary add invalid categories as packages.
 .TP
 \fBPORTDIR_OVERLAY\fR = \fI"[path] [different\-path] [etc...]"\fR
 Defines the directories in which user made ebuilds may be stored and not