From owner-freebsd-questions@FreeBSD.ORG Sat Dec 11 01:50:43 2004 Return-Path: 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 BC2BF16A4DA for ; Sat, 11 Dec 2004 01:50:43 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1382443D31 for ; Sat, 11 Dec 2004 01:50:42 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend2.messagingengine.com (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 326FDC40FD5 for ; Fri, 10 Dec 2004 20:50:41 -0500 (EST) X-Sasl-enc: QDYFy/f+cJXWKpEK0y7sBw 1102729836 Received: from gumby.localhost (unknown [80.41.121.0]) by frontend2.messagingengine.com (Postfix) with ESMTP id B62FD56F785 for ; Fri, 10 Dec 2004 20:50:36 -0500 (EST) From: RW To: freebsd-questions@freebsd.org Date: Sat, 11 Dec 2004 01:51:46 +0000 User-Agent: KMail/1.7.1 References: <20041210145456.GB74945@dogma.freebsd-uk.eu.org> In-Reply-To: <20041210145456.GB74945@dogma.freebsd-uk.eu.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412110151.47332.list-freebsd-2004@morbius.sent.com> Subject: Re: When to use 'portupgrade -R' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 01:50:44 -0000 On Friday 10 December 2004 14:54, Jonathon McKitrick wrote: > I've run into some problems using 'portupgrade -R' so I'm wondering if just > using 'portupgrade' is good enough in most cases. I don't want a port to > be upgraded without NECESSARY dependencies, but I don't want minor upgrades > done UNNECESSARILY that might cause inconsistencies in the database. If your intent is to add a few new "bells and whistles" to fairly self-contained ports between clean installs of the OS, and you are not too worried by stability and security, then this is a reasonable strategy. In the long-term it's best to keep all your ports reasonably up-to-date, and to follow UPDATING. When you get a package database problem from a minor update it's usually a repeat of a problem you have already fixed, So either you already know how to fix it, or you can take comfort from the fact that it'll come around again soon.