From owner-freebsd-questions@FreeBSD.ORG Sun Dec 23 00:19:29 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 668B416A417 for ; Sun, 23 Dec 2007 00:19:29 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from smtp.infidyne.com (ds9.infidyne.com [88.80.6.206]) by mx1.freebsd.org (Postfix) with ESMTP id 3627713C461 for ; Sun, 23 Dec 2007 00:19:29 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se (c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se [85.229.22.130]) by smtp.infidyne.com (Postfix) with ESMTP id 964EE77FD4; Sun, 23 Dec 2007 01:19:27 +0100 (CET) From: Peter Schuller To: freebsd-questions@freebsd.org Date: Sun, 23 Dec 2007 01:19:21 +0100 User-Agent: KMail/1.9.7 References: <221c791e0712220839v67a02e78q7cd5519f9b05a210@mail.gmail.com> In-Reply-To: <221c791e0712220839v67a02e78q7cd5519f9b05a210@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2614645.98ls3eoqfJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200712230119.30705.peter.schuller@infidyne.com> Cc: Robe Subject: Re: Updating ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 00:19:29 -0000 --nextPart2614645.98ls3eoqfJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > What's the difference between them? The main difference that is relevant to me personally is that portmanager=20 makes no attempt to be too smart about avoiding compilation, and it is full= y=20 restartable without affecting the results. It rebuilds ports in such a way that the result is, in theory, supposed to = be=20 equivalent to what you would have gotten had you installed them all from=20 scratch with your current ports tree. In particular, given a re-build (e.g. upgraded) port X, all ports depending= on=20 X will also be re-built regardless of whether that is required according to= =20 the dependency relation. This is handled in such a way that it is not=20 dependent on the entire procedure completing in one session, as you are wit= h=20 portupgrade (meaning it's restartable, as mentioned above). In practice, I find this is the most useful upgrading method. I have never= =20 been able to use portupgrade for more than a week or two on a real machine= =20 without running into issues (stale dependencies, failed builds due to weak= =20 dependency information, etc). That said, it's not perfect. The implementation is buggy in some ways, and= =20 there are fundamental problems with that upgrading approach (e.g., files=20 moving between packages can cause problems). In the end I tend to either build binary packages from scratch and use=20 portupgrade -afPP to upgrade, or do in-place upgrading with portmanager. =2D-=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --nextPart2614645.98ls3eoqfJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHbamSDNor2+l1i30RAtV2AJwLzC5wN1K4SlkoeqBpw/4y8AipMACZAVrr XWxRUXKk0H4tBFyOzuZIXRo= =xpWI -----END PGP SIGNATURE----- --nextPart2614645.98ls3eoqfJ--