From owner-freebsd-ports@FreeBSD.ORG Mon Jan 10 15:54:12 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 069F916A4CE for ; Mon, 10 Jan 2005 15:54:12 +0000 (GMT) Received: from web53601.mail.yahoo.com (web53601.mail.yahoo.com [206.190.37.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 6A1E343D53 for ; Mon, 10 Jan 2005 15:54:11 +0000 (GMT) (envelope-from scott@sremick.net) Received: (qmail 87653 invoked by uid 60001); 10 Jan 2005 15:54:10 -0000 Message-ID: <20050110155410.87651.qmail@web53601.mail.yahoo.com> Received: from [65.213.7.6] by web53601.mail.yahoo.com via HTTP; Mon, 10 Jan 2005 07:54:10 PST X-RocketYMMF: siremick Date: Mon, 10 Jan 2005 07:54:10 -0800 (PST) From: "Scott I. Remick" To: "Michael C. Shultz" In-Reply-To: <200501061923.51190.reso3w83@verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-ports@freebsd.org Subject: Portmanager update X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: scott@sremick.net List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 15:54:12 -0000 Michael, Just an update: I had portupgrade -aRf running for a few days. I suffered a lock-up at one point so I used the -x flag in-conjuntion with a >= date field the 2nd time aroudn to exclude those that had already built. That finished and I have now had portmanager -u running for a few days. It's still clipping along. One thing I noticed w/ portmanager is that it's intolerant of any failures. Unlike portupgrade which will continue to compile other ports if one fails (skipping any additional ports that depended on the failed port), portmanager just stops if anything fails. A few ports that have known build issues with their newer versions I had to completely uninstall in order to get portmanager to proceed, despite the currently-installed versions working just fine. Examples: mplayer, flightgear (simgear). I would've rather had portmanager skip mplayer and anything that depended on it (nothing) instead of having to uninstall the working version, because then I could've still had a working (albeit older) one installed. Another issue I discovered with portmanager is when it depends on an older version of something when you're using a newer version, and both are in the ports tree and can't be both installed at the same time. For example: linexplore depends on Samba 2. I use Samba 3. With pkgdb -F I could forced Linexplore to depend on Samba 3 instead but the new method is to never use that. So what is one to do in a situation like this? I removed linexplore for now. I also used to use linuxbase8 when everything depended on linuxbase7, although that apparently has changed and 8 is the new default. Anyhow, thanks for your help on this... it's greatly appreciated.