From owner-freebsd-questions@FreeBSD.ORG Sat Jul 9 20:04:19 2011 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 19552106564A for ; Sat, 9 Jul 2011 20:04:18 +0000 (UTC) (envelope-from tomdean@speakeasy.org) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.50]) by mx1.freebsd.org (Postfix) with ESMTP id AFF1A8FC08 for ; Sat, 9 Jul 2011 20:04:18 +0000 (UTC) Received: (qmail 766 invoked from network); 9 Jul 2011 20:04:18 -0000 Received: from 24-113-112-30.wavecable.com (HELO [192.168.2.2]) (tomdean@[24.113.112.30]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 9 Jul 2011 20:04:17 -0000 From: "Thomas D. Dean" To: freebsd-questions@freebsd.org In-Reply-To: <20110709214500.19c7c774.freebsd@edvax.de> References: <1310231643.10903.15.camel@asus> <4E189ACC.1090101@xaerolimit.net> <1310236380.10903.22.camel@asus> <20110709204737.0155d911.freebsd@edvax.de> <1310238355.10903.36.camel@asus> <1310239932.10903.46.camel@asus> <20110709214500.19c7c774.freebsd@edvax.de> Content-Type: text/plain; charset="UTF-8" Organization: Home Date: Sat, 09 Jul 2011 13:04:17 -0700 Message-ID: <1310241857.10903.63.camel@asus> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Subject: Re: Portupgrade Package Question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tomdean@speakeasy.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jul 2011 20:04:19 -0000 On Sat, 2011-07-09 at 21:45 +0200, Polytropon wrote: > > If I understood everything correctly, CVS (csup) and portsnap > do both follow "the one tree" which gets frequently updated, > and by the tag specified above you'll always get the current > version of the tree. Getting older versions (e. g. the RELEASE > tree) involves specifying a different tag, or loading it from > the installation media directly. > > The difference is that changes in the ports tree are reflected > much faster in the CVS method than in the portsnap approach, > which may "lag" a bit. However, portsnap seems to work faster > and to perform better than CVS. It's also worth mentioning that > it seems to fit better to the "building cycle" of the -stable > ports to become precompiled packages (that you request using > the -PP parameter, similar to the use of pkg_add -r in case of > installation instead of update). > > But if you require the most recent ports tree, using CVS seems > to be the better method. As you're updating binary, but with > using the ports tree (portupgrade relies on that, pkg_add for > example doesn't), you should make sure to always have the > current version if you follow the stable OS branch. > I have always built ports from the source. I decided to try binary ports for things I have not modified. I cannot seem to get portupgrade to use the definitions I set in etc/pkgtools.conf. For the most recent try, I have ... # OS_PATCHLEVEL: "" "-p8" # OS_PLATFORM: "i386" "amd64" # OS_PKGBRANCH: "7-current" "6.1-release" OS_RELEASE="8-STABLE" OS_BRANCH="STABLE" OS_PKGBRANCH="8-stable" # Useful predefined functions: # # localbase() # Returns LOCALBASE. ... But, portupgrade still tries to fetch from 8.2-release. If I want to use binary ports it looks like I need to zap the ports tree and recreate it with portsnap. tomdean