summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorjkh <jkh@FreeBSD.org>1997-03-10 11:37:54 +0000
committerjkh <jkh@FreeBSD.org>1997-03-10 11:37:54 +0000
commit91e039579379ab3cce6bafbea7e1b45a5584d4f5 (patch)
tree1a8f62c6c0741a9cb37a3d24e692c580db09ac0b /README
parent221e51073dd421b3987e42155c740edbe9222448 (diff)
downloadFreeBSD-ports-91e039579379ab3cce6bafbea7e1b45a5584d4f5.zip
FreeBSD-ports-91e039579379ab3cce6bafbea7e1b45a5584d4f5.tar.gz
Note that the ports collection can eat disk space during its lifetime.
Diffstat (limited to 'README')
-rw-r--r--README10
1 files changed, 10 insertions, 0 deletions
diff --git a/README b/README
index c5633d7..79a8f91 100644
--- a/README
+++ b/README
@@ -19,3 +19,13 @@ for the latest official version from FreeBSD-current.
The section "The Ports Collection" will tell you how to use the
ports and packages and the "Porting Applications" section
describes how one can contribute to the ports collection.
+
+NOTE: This tree can GROW significantly in size during normal usage!
+The distribution tar files can and do accumulate in /usr/ports/distfiles,
+and the individual ports will also use up lots of space in their work
+subdirectories unless you remember to "make clean" after you're done
+building a given port. /usr/ports/distfiles can also be periodically
+cleaned without ill-effect, though if you don't have the original
+distribution tarball(s) for something on CDROM then you will need to pull
+it all over your network connection again if you ever try to build the
+associated port.
OpenPOWER on IntegriCloud