Date: Thu, 08 Nov 2007 22:15:37 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Kris Kennaway <kris@freebsd.org>, Matthew Seaman <m.seaman@infracaninophile.co.uk>, Mario Lobo <mario.lobo@ipad.com.br>, freebsd-questions@freebsd.org Subject: Re: About Freebsd 7.0 versus 6.3 Message-ID: <47337C79.2020201@FreeBSD.org> In-Reply-To: <20071108210856.GA70286@slackbox.xs4all.nl> References: <200711081455.39635.cesar@expresso.com.br> <bef9a7920711080928t76efabaaw4af6c85be7fb03a@mail.gmail.com> <200711081448.48390.mario.lobo@ipad.com.br> <20071108183239.GA65453@slackbox.xs4all.nl> <4733633E.2050800@infracaninophile.co.uk> <20071108195436.GA67970@slackbox.xs4all.nl> <47337256.8040805@FreeBSD.org> <20071108210856.GA70286@slackbox.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Roland Smith wrote: > On Thu, Nov 08, 2007 at 09:32:22PM +0100, Kris Kennaway wrote: > >>>> You don't need to delete all the ports in one go and then reinstall >>>> them in another: running 'portupgrade -fa' will do the job. >>> Port upgrade tools are not guaranteed to work perfectly in this >>> situation. I tried doing an update with portmanager and ended up with >>> some binaries linked against both libc.so.6 and libc.so.7! Some ports >>> didn't even compile. >> portmanager isn't recommended for use since it became abandonware a long >> time ago and never reached maturity. If you (correctly ;) use portupgrade >> (e.g. -fa or -faP) then you will not have this problem. > > Dang, I meant portmaster, not portmanager. My bad. I would say that portmaster is still in the maturing phase also, although it has made recent progress. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47337C79.2020201>