Date: Thu, 11 Dec 2008 22:13:00 -0500 From: Peter Beckman <beckman@angryox.com> To: freebsd-ports@freebsd.org Subject: portupgrade and freebsd-update: A better way? Message-ID: <alpine.BSF.2.00.0812112159350.82765@nog.angryox.com>
next in thread | raw e-mail | index | archive | help
So I took on binary upgrading one of my FreeBSD servers today from
6.2-RELEASE to 7.0-RELEASE. Many useful sites outline exactly how to do
this right, and they are mostly useful.
Except when it comes to ports.
http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html
http://www.cyberciti.biz/faq/howto-freebsd-server-upgrades/
You get a few production servers with 200+ ports installed, and upgrading
could take several days and lots of headaches and a lot of babysitting.
Is there some sort of automated way that someone smart has figured out how
to determine which ports are actually affected by the upgrade, so I only
have to upgrade a hopefully small subset of installed ports? Are ALL the
libraries upgraded during the OS upgrade modified in a way that breaks ALL
existing ports? My gut says no, but my brain says it's not trivial to
match the two together to limit the number of times you have to rebuild a
port.
Is there a better way? Does portsnap or portmanager or portupgrade keep
track? What have I missed?
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman@angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0812112159350.82765>