Date: Tue, 05 Sep 2006 17:53:35 -0400 From: Gerard Seibert <gerard@seibercom.net> To: freebsd-questions@freebsd.org Subject: Re: Various package/ports problems Message-ID: <20060905174924.60F5.GERARD@seibercom.net> In-Reply-To: <44FDE33E.10906@childeric.freeserve.co.uk> References: <20060905035751.16474.qmail@web53407.mail.yahoo.com> <44FDE33E.10906@childeric.freeserve.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Whitehouse wrote:
> Dr. Jennifer Nussbaum wrote:
>
> > So now i can find out what version each port is, but that doesnt
> > help me know whether these are outdated, or to update them.
> > For that im still stuck on the Ruby core dump problem. I did
> > reinstall portupgrade, ruby18, and the ruby-bdb thing, but sadly
> > i still get the same abort trap/core dump thing ive reported all
> > along. Is there any other way i can attack this last issue?
> >
> > Thanks.
> >
> > Jen
>
> Have you tried portmanager (sysutils/portmanager)? The -s option just
> reports on what's required to upgrade.
Assuming you have a freshly updated ports tree, you could also just run
this little command:
/usr/sbin/pkg_version -vIL=
It will display what needs to be updated very quickly. I think that
'portmanager' would be the best way to update the ports however.
--
Gerard Seibert
gerard@seibercom.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060905174924.60F5.GERARD>