Date: Wed, 24 Jun 2009 01:50:51 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: upgrading installed ports: time to do it ? Message-ID: <20090624015051.2ee23577@gumby.homeunix.com> In-Reply-To: <4A414751.9090804@onetel.com> References: <200906212038.39370.meslists@yahoo.fr> <b79ecaef0906211307g7be0d5baob2b1cf279dac3c5b@mail.gmail.com> <4A3FE271.8080201@onetel.com> <20090622214802.0761813e@gumby.homeunix.com> <4A414751.9090804@onetel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 23 Jun 2009 22:21:21 +0100 Chris Whitehouse <cwhiteh@onetel.com> wrote: > RW wrote: > > On Mon, 22 Jun 2009 20:58:41 +0100 > > Chris Whitehouse <cwhiteh@onetel.com> 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. > > Not trolling but can you give me some examples? Many of of the entries aren't solely to do with guiding portmaster/portupgrade through the upgrade, they may also involve migrating configuration or user data, or performing other administrative tasks. Portmanger does cope with most of the "portupgrade -o" and "portupgrade -r" entries, although sometime it will need to be run (or rerun) in pristine-mode. However, it doesn't always work correctly when software has been repackaged because this can create temporary unrecorded conflicts which are difficult for any tool to deal with. If you see any instructions to remove packages before upgrading, it's prudent to follow them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090624015051.2ee23577>