Date: Sat, 13 May 2006 23:29:59 +0100 From: Aren Olvalde Tyr <aren.tyr@gawab.com> To: freebsd-questions@freebsd.org Subject: Re: Cvsup verses Portsnap Message-ID: <200605132330.08793.aren.tyr@gawab.com> In-Reply-To: <000301c676b3$9f398b90$6603a8c0@zeus> References: <000301c676b3$9f398b90$6603a8c0@zeus>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1530958.FORkBO8vSK Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 13 May 2006 18:35, Tom Moore wrote: > Hi guys. > Which program is best for retrieving and keeping the ports tree up to dat= e? > What are some pros and cons of each approach? > Is one method better than the other? Both systems are very efficient and work extremely well, so you won't go to= o=20 far wrong with either. However, I believe Portsnap has the edge and uses le= ss=20 bandwidth. Keeping your Ports tree up to date with Portsnap is as simple as #portsnap fetch && portsnap update Aren. --nextPart1530958.FORkBO8vSK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEZl3woWGxb6IQ4B4RAr9mAJ4hXbFydoFgVSRsyqRUItrUpdbAJACgm4kI KovQmJCHPDVkl5oWugV3e70= =MEew -----END PGP SIGNATURE----- --nextPart1530958.FORkBO8vSK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605132330.08793.aren.tyr>