From owner-freebsd-questions@FreeBSD.ORG Thu Apr 16 10:17:12 2009 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 993101065672 for ; Thu, 16 Apr 2009 10:17:12 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 5E68F8FC1B for ; Thu, 16 Apr 2009 10:17:12 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (gate.lan.rachie.is-a-geek.net [192.168.2.10]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id C3D7D7E818; Thu, 16 Apr 2009 02:17:10 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Thu, 16 Apr 2009 12:17:08 +0200 User-Agent: KMail/1.11.0 (FreeBSD/8.0-CURRENT; KDE/4.2.0; i386; ; ) References: <49E64867.5060209@gmail.com> <20090416051505.GA88637@slackbox.xs4all.nl> In-Reply-To: <20090416051505.GA88637@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904161217.08784.mel.flynn+fbsd.questions@mailing.thruhere.net> Cc: Roland Smith , "Eugene L." Subject: Re: FreeBSD Upgrade: Ports That Need Rebuilding 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: Thu, 16 Apr 2009 10:17:12 -0000 On Thursday 16 April 2009 07:15:05 Roland Smith wrote: > On Thu, Apr 16, 2009 at 12:49:43AM +0400, Eugene L. wrote: > > I am planning to update to CURRENT, been reading freebsd-current for > > some time, apparently some ports require rebuilding as they are kernel > > specific, like hal, so I wonder how to rebuild those ports automatically? > > If you switch to another major version of FreeBSD, the best course is to > remove and reinstall all ports. All ports depending on libc. Which is everything except scripts. Removal isn't necessary. ports-mgmt/portmaster is one of those scripts that doesn't need recompilation and can be used to force recompilation of all ports that need it. Two for one deal. I personally do make delete-old-libs /before/ recompiling ports this way, because 1) I'm sure a port doesn't link to an old library and 2) the ports that failed will complain more loudly. However, when you're doing this for the first time, it's not a bad idea to make a seperate slice for current and cross-install on there (the procedure is documented in /usr/src/UPDATING). It's trivial to look at the stable slice's /var/db/pkg and install all those ports, then copy over configuration files. /home can be share without problems, providing you create the users again with the same uid. The advantage is that you have a workable system to fall back on whenever -current breaks something you need. -- Mel