From owner-freebsd-current@FreeBSD.ORG Wed Oct 27 14:06:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F18D916A4CE for ; Wed, 27 Oct 2004 14:06:02 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2B2543D46 for ; Wed, 27 Oct 2004 14:06:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4DBF5521A6; Wed, 27 Oct 2004 07:07:05 -0700 (PDT) Date: Wed, 27 Oct 2004 07:07:05 -0700 From: Kris Kennaway To: Andre Guibert de Bruet Message-ID: <20041027140705.GA26376@xor.obsecurity.org> References: <20041027003640.K42571@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20041027003640.K42571@alpha.siliconlandmark.com> User-Agent: Mutt/1.4.2.1i cc: Zoltan Frombach cc: freebsd-current@freebsd.org Subject: Re: Portupgrade -af question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2004 14:06:03 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 27, 2004 at 12:48:52AM -0400, Andre Guibert de Bruet wrote: > >installed ports. But this would take a whole day, especially since it's= =20 > >just a single processor Pentium III system. Shouldn't it be faster to le= t=20 > >portupgrade use pre-compiled packages (either from a 5.3-RELEASE install= =20 > >CD or from a remote site)? Something like: 'portupgrade -afP' ? Would it= =20 > >work? This would save a lot of time... a lot of down-time, in fact. >=20 > This is guaranteed to work if: > - Your ports skeleton is up to date. > - This machine has HTTP and FTP access enabled. > - The ports you are upgrading are not forbidden, deprecated or broken. > - All distfiles are available from at least one of the relevant mirrors. >=20 > This is the case because portupgrade -P searches for packages locally or= =20 > wherever PKG_PATH points to, tries to use pkg_fetch and then falls back t= o=20 > updating from ports if precompiled packages are not available. Also, if you're using non-default compile options for ports (e.g. setting WITH_*/WITHOUT_* or other control variables), you won't get this if you update with the package (which are built with default options). Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBf6uIWry0BWjoQKURAjGlAKD+Ix8wunF/pDS8fYqnQO73bWWKzwCgltBq ZC9plkIx3qg8v8bkLh2G6V4= =e6l1 -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--