summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlec Warner <antarus@gentoo.org>2008-01-19 23:18:12 +0000
committerAlec Warner <antarus@gentoo.org>2008-01-19 23:18:12 +0000
commitbcf12c6f26cf9632c95a478ce7f9ad1175ef8eee (patch)
tree6c1bc292fd05b8ce0e38d147855f01ca0c360013
parente46e777438bc16ee1e141b43aab50d05a6e42a23 (diff)
downloadportage-bcf12c6f26cf9632c95a478ce7f9ad1175ef8eee.tar.gz
portage-bcf12c6f26cf9632c95a478ce7f9ad1175ef8eee.tar.bz2
portage-bcf12c6f26cf9632c95a478ce7f9ad1175ef8eee.zip
Add a note that PORTDIR is a repository of software and that users should not add random directories in it.
svn path=/main/trunk/; revision=9209
-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 42182a826..e02bcd9eb 100644
--- a/man/make.conf.5
+++ b/man/make.conf.5
@@ -456,7 +456,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