aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJordan K. Hubbard <jkh@FreeBSD.org>1997-06-11 09:06:37 +0000
committerJordan K. Hubbard <jkh@FreeBSD.org>1997-06-11 09:06:37 +0000
commitfaf3874d859a4db1e04410064cb561429a3c1af9 (patch)
treef3ffc7d98f656c781edd62c989303d774f3facc0 /README
parenta1ee99424f571697d43d2f2ce84a2d0c5fe9db19 (diff)
downloadports-faf3874d859a4db1e04410064cb561429a3c1af9.tar.gz
ports-faf3874d859a4db1e04410064cb561429a3c1af9.zip
Notes
Diffstat (limited to 'README')
-rw-r--r--README8
1 files changed, 8 insertions, 0 deletions
diff --git a/README b/README
index 79a8f917f26a..f71d9b1ed688 100644
--- a/README
+++ b/README
@@ -20,6 +20,13 @@ 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.
+If you would like to search for a given port, you can do so easily
+by saying:
+
+ make search key="<keyword>"
+
+Which will generate a list of all ports matching <keyword>.
+
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
@@ -29,3 +36,4 @@ 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.
+