summaryrefslogtreecommitdiffstats
path: root/sysutils
diff options
context:
space:
mode:
authorcperciva <cperciva@FreeBSD.org>2005-01-16 01:24:26 +0000
committercperciva <cperciva@FreeBSD.org>2005-01-16 01:24:26 +0000
commitb18ab42558d683bdad131d1d80a97a9b84a10e20 (patch)
tree8fa28df7ee74a07cbc2c2060cd2d68a79b3f6aae /sysutils
parent05a95562edb41f3db9a5c215fc5314dc9811d9da (diff)
downloadFreeBSD-ports-b18ab42558d683bdad131d1d80a97a9b84a10e20.zip
FreeBSD-ports-b18ab42558d683bdad131d1d80a97a9b84a10e20.tar.gz
In light of recent tests, update the description of portsnap to note
that it is far more bandwidth-efficient than CVSup in cases where the ports tree is being updated every few days. Approved by: pav
Diffstat (limited to 'sysutils')
-rw-r--r--sysutils/portsnap/pkg-descr5
1 files changed, 3 insertions, 2 deletions
diff --git a/sysutils/portsnap/pkg-descr b/sysutils/portsnap/pkg-descr
index 8b36901..a33c0a7 100644
--- a/sysutils/portsnap/pkg-descr
+++ b/sysutils/portsnap/pkg-descr
@@ -5,8 +5,9 @@ half of that system; it downloads compressed snapshots into
a ports tree into /usr/ports ("portsnap extract") or update an
existing tree ("portsnap update").
-Portsnap uses bandwidth roughly comparable to CVSup, but operates
-entirely over HTTP.
+In addition to operating entirely over HTTP, portsnap can use under
+a tenth of the bandwidth required by CVSup if a copy of the ports
+tree is being updated every few days.
WWW: http://www.daemonology.net/portsnap/
OpenPOWER on IntegriCloud