summaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2008-01-31 07:55:17 +0000
committerZac Medico <zmedico@gentoo.org>2008-01-31 07:55:17 +0000
commit6b2bd7703e5416f33c5d62584d691252884b9382 (patch)
tree4fd0462ce436ba220d9d604044a1e8e9e94df607 /man
parent70e65f34ca274abb8a81005dc9674e3c9fac9037 (diff)
downloadportage-6b2bd7703e5416f33c5d62584d691252884b9382.tar.gz
portage-6b2bd7703e5416f33c5d62584d691252884b9382.tar.bz2
portage-6b2bd7703e5416f33c5d62584d691252884b9382.zip
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
Diffstat (limited to 'man')
-rw-r--r--man/make.conf.54
1 files changed, 3 insertions, 1 deletions
diff --git a/man/make.conf.5 b/man/make.conf.5
index 220d045d7..072f24e8e 100644
--- 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