Date: Fri, 29 Jun 2007 20:07:52 -0400 From: r17fbsd@xxiii.com To: "Michael P. Soulier" <msoulier@digitaltorque.ca>, freebsd-questions@freebsd.org Subject: Re: running portupgrade -a Message-ID: <6.2.3.4.2.20070629200108.01e12e00@mailsvr.xxiii.com> In-Reply-To: <20070629231452.GK18911@tigger.digitaltorque.ca> References: <20070629231452.GK18911@tigger.digitaltorque.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
At 07:14 PM 6/29/2007, you wrote:
>So, is running portupgrade -a a good idea, as you likely haven't
>checked for issues
>for your system?
I just started using portupgrade recently, and no, I would NOT let it
rip with the --all option.
I find it's most useful for the libraries and required packages that
don't need any compile-time options nor config files. Those sorta
things I install from packages anyway. So I started with a list of
stuff that required compile time control and/or configuration. "ls
/var/db/ports" and pkg-info are a good start... Then run
"portupgrade -aiP" -i asks for confirmation on each, and -P tries to
get it from packages (binary) rather than ports. Let that update all
the "background" junk.
Than go back and research and possibly manually remake & install the
primary apps (eg: apache, samba, squid, in my case.)
HTH, -RW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.3.4.2.20070629200108.01e12e00>