From owner-freebsd-questions@FreeBSD.ORG Mon Jun 22 22:35:03 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 C15A31065670 for ; Mon, 22 Jun 2009 22:35:03 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from QMTA02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 6D11B8FC0C for ; Mon, 22 Jun 2009 22:35:03 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from OMTA03.westchester.pa.mail.comcast.net ([76.96.62.27]) by QMTA02.westchester.pa.mail.comcast.net with comcast id 731X1c00k0bG4ec52Ab3o0; Mon, 22 Jun 2009 22:35:03 +0000 Received: from comcast.net ([98.203.142.76]) by OMTA03.westchester.pa.mail.comcast.net with comcast id 7Ab01c0121f6R9u3PAb1Td; Mon, 22 Jun 2009 22:35:03 +0000 Received: by comcast.net (sSMTP sendmail emulation); Mon, 22 Jun 2009 15:34:59 -0700 Date: Mon, 22 Jun 2009 15:34:59 -0700 From: Charlie Kester To: freebsd-questions@freebsd.org Message-ID: <20090622223459.GA75560@comcast.net> Mail-Followup-To: freebsd-questions@freebsd.org References: <200906212038.39370.meslists@yahoo.fr> <4A3FE271.8080201@onetel.com> <20090622214802.0761813e@gumby.homeunix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20090622214802.0761813e@gumby.homeunix.com> X-Mailer: Mutt 1.5.20 X-Composer: VIM 7.2 User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: upgrading installed ports: time to do it ? 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: Mon, 22 Jun 2009 22:35:04 -0000 On Mon 22 Jun 2009 at 13:48:02 PDT RW wrote: >On Mon, 22 Jun 2009 20:58:41 +0100 >Chris Whitehouse wrote: > >> I'll probably get flamed for this but since I've been using >> ports-mgmt/portmanager I've almost forgotten >> about /usr/ports/UPDATING and all that pkgdb -Fu stuff or whatever it >> was. I've upgraded ports just by doing 'portmanager -u' over one or >> two quite major changes and not had any problems that haven't been >> down to an individual ports. > >You still need to read UPDATING, portmanager handles some of the issues >automatically, but not all. that durned human element again! would be nice if a port upgrade tool did that for you, displayed any entries related to ports that need updating, and gave you a chance to postpone the update until you've taken whatever actions UPDATING suggests would require UPDATING to be written in a consistent, machine-readable format