From owner-freebsd-ports@FreeBSD.ORG Tue Nov 15 17:15:14 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11B531065690 for ; Tue, 15 Nov 2011 17:15:14 +0000 (UTC) (envelope-from sterling@camdensoftware.com) Received: from wh1.interactivevillages.com (ca.2e.7bae.static.theplanet.com [174.123.46.202]) by mx1.freebsd.org (Postfix) with ESMTP id CDB788FC1F for ; Tue, 15 Nov 2011 17:15:13 +0000 (UTC) Received: from 184-78-197-203.war.clearwire-wmx.net ([184.78.197.203] helo=_HOSTNAME_) by wh1.interactivevillages.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1RQMIc-0003P0-7A for freebsd-ports@freebsd.org; Tue, 15 Nov 2011 08:55:31 -0800 Received: by _HOSTNAME_ (sSMTP sendmail emulation); Tue, 15 Nov 2011 08:55:52 -0800 Date: Tue, 15 Nov 2011 08:55:52 -0800 From: Chip Camden To: freebsd-ports@freebsd.org Message-ID: <20111115165552.GC18788@libertas.local.camdensoftware.com> Mail-Followup-To: freebsd-ports@freebsd.org References: <20111115094823.GA9461@sh4-5.1blu.de> <4EC2466B.3020808@infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8X7/QrJGcKSMr1RN" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Company: Camden Software Consulting URL: http://camdensoftware.com X-PGP-Key: http://pgp.mit.edu:11371/pks/lookup?search=0xD6DBAF91 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wh1.interactivevillages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - camdensoftware.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: cvs checkout ./. csup X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2011 17:15:14 -0000 --8X7/QrJGcKSMr1RN Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoth Daniel Nebdal on Tuesday, 15 November 2011: > On Tue, Nov 15, 2011 at 12:00 PM, Matthew Seaman > wrote: > > On 15/11/2011 09:48, Matthias Apitz wrote: > >> Since many years I'm fetching or updating /usr/ports with > >> > >> # cd /usr > >> # setenv CVSROOT :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs > >> # cvs checkout ports > >> > >> and later do the updating just with: > >> > >> # cd /usr/ports > >> # cvs update > >> # portupgrade -ai > >> > >> The FreeBSD handbook describes (or recommends?) using 'csup' for > >> updating ports tree... What is the advantage (or reason, if any)? > > > > Efficiency, basically. =A0csup should require less bandwidth and put le= ss > > load on servers than using cvs directly. =A0It works like rsync, only > > transferring the parts of the files that changed but exploiting the cvs > > revision history to produce more specific and minimal deltas than you > > can get just by using the standard rsync algorithm. > > > > However csup(1) doesn't give you any of the VCS features you'ld get by > > doing a cvs checkout -- so no simple way to diff a local copy against > > the repo, etc. etc. 'cvs checkout' of all or parts of the ports is still > > frequently preferable for developing rather than just using the ports. > > > > There are also many more cvsup servers worldwide than there are anon-cvs > > servers. > > >=20 > There's also portsnap, which has been in the base system for a while > now. It has some of the same drawbacks as csup/cvsup (no VCS > features), but is in my experience faster than them. In short, you can > use "portsnap fetch extract" to download a complete compressed tarball > of current ports and extract it, and after doing that you can use > "portsnap fetch update" to update to the current state. Read the > manpage; there are some important details. >=20 > It uses a binary patch system that's quite efficient, so if you just > want an updated /usr/ports , it's probably the fastest solution. (I > think the exact method is that "fetch" grabs a tarball if it doesn't > exist. If it does exist, it gets the binary patches required to update > it to the current state. With it in place, "extract" unpacks the > entire thing, and "update" only extracts the files touched by the last > "fetch"-command.) >=20 > It has a handbook page: http://www.freebsd.org/doc/handbook/portsnap.html >=20 In my experience, portsnap is much faster than csup for updating ports. I've tried both (at different times) updating almost daily for months at a time. --=20 =2EO. | Sterling (Chip) Camden | http://camdensoftware.com =2E.O | sterling@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com --8X7/QrJGcKSMr1RN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iQEcBAEBAgAGBQJOwpmYAAoJEIpckszW26+RZuIH/jHh5NgXfWAOJwYtc7JKgYlr v++pYZvhLibVHCc/p1tUTW2RAkhmN4GVucJDZIYEeq86QMuSiLcoNT5zlRqDHgfo n5bP/MHwhUFi+OuTB//FL7v1+w/qvH8ThGrMmrWSEyIBmarVPAsSCV7sw1BLAnSu 2lnweO3506r041y2oIZiT8QpsHsreA+MVQi0ki0cQBQrYKVFGZrtPwUAseF1EEKI pv3sDn7EpbM9fsgSuS7vy14fRykMVlbibknoz9hpZFvGya84Tunn2q2DjExwx5ov gxDVb/m7DfJ1ghBLJLwO7MyvS2BddTrFAOzR5GGFlgnVwzHCnqayU57y6kl/Veo= =zD6V -----END PGP SIGNATURE----- --8X7/QrJGcKSMr1RN--