From owner-freebsd-questions@FreeBSD.ORG Sat Jun 25 16:42:46 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 417D116A41C for ; Sat, 25 Jun 2005 16:42:46 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out6.blueyonder.co.uk (smtp-out6.blueyonder.co.uk [195.188.213.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2D4443D1D for ; Sat, 25 Jun 2005 16:42:45 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.37.55] ([82.41.37.55]) by smtp-out6.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Sat, 25 Jun 2005 17:43:25 +0100 Message-ID: <42BD8983.1000303@dial.pipex.com> Date: Sat, 25 Jun 2005 17:42:43 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: =?ISO-8859-1?Q?Erik_N=F8rgaard?= References: <20050625112256.GA32433@lothlorien.nagual.st> <42BD41CC.70202@locolomo.org> In-Reply-To: <42BD41CC.70202@locolomo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 25 Jun 2005 16:43:25.0871 (UTC) FILETIME=[01EB9BF0:01C579A5] Cc: freebsd-questions Subject: Re: upgrading all 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: Sat, 25 Jun 2005 16:42:46 -0000 Erik N=F8rgaard wrote: > Dick Hoogendijk wrote: > >> I want to do a portupgrade on all installed ports. >> >> What's the right way? >> "portupgrade -arR ?" >> or >> "portupgrade -a" ? >> >> I hesitate and don't want to screw up my machine. >> > portupgrade isn't suitable for upgrading the entire machine, even=20 > though you do recursive and Recursive. What, in your opinion, makes it unsuitable? I've used portugrade=20 exclusively and never had trouble. Portmanager, on the other hand, core dumped the very first time I ran=20 it. A send-pr was closed with a message to contact the port maintainer, = and an email to the port maintainer never received a reply. Didn't=20 exactly inspire my confidence. In reply to the original question, I would use -arR, but only after=20 reading /usr/ports/UPDATING. If there are a lot to do, I tend to only=20 do a few at a time. Nor do I ever "automate" the process by trying to=20 run it from a cronjob or similar, a) because some ports have a habit of=20 stopping to ask you questions and b) because I don't always want to=20 upgrade everything. If something is critical to me (e.g. Mozilla) I=20 want the time to evaluate that the upgrade worked, and not have it=20 happen without me realising right in the middle of being busy with=20 something more important. --Alex