Date: Fri, 23 Jul 2010 21:20:16 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Martin Koch Andersen <martin@925.dk> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-install upgrade, how many install phases required Message-ID: <4C49F980.8060008@infracaninophile.co.uk> In-Reply-To: <165F7744-37AD-42F9-AB0B-3E1E1855D09E@925.dk> References: <165F7744-37AD-42F9-AB0B-3E1E1855D09E@925.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6457A5B2001872FE63BC22CC Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 23/07/2010 17:19:54, Martin Koch Andersen wrote: > Hi, >=20 > Will freebsd-install upgrade tell you, if any libraries version numbers= got bumped, and thus if installed packages needs rebuilding? >=20 > I followed the handbook and did the 8.0-RELEASE to 8.1-RELEASE upgrade = like: >=20 > freebsd-update -r 8.1-RELEASE upgrade > freebsd-update install > shutdown -r now > freebsd-update install freebsd-update only updates the *base* system. It doesn't update the ports tree at all. For that, you need portsnap, which works very much like freebsd-update (or else one of a number of alternatives like csup(1), which work differently.) Once you've updated the ports tree using portsnap (or whatever) then you can update your installed ports from it, which is where tools like portupgrade(1) or portmaster(1) come in. portupgrade(1) won't find any work to do unless you have run portsnap first. > And then: >=20 > portupgrade -af > freebsd-update install > shutdown -r now >=20 > But was this last round of rebuilding installed ports etc. really neede= d? Or would the second "freebsd-update install" have told me if it was? I= n any case, the last "freebsd-update install" did nothing. If the OS major version is the same, then the shlib ABI version on all the shlibs in the base system is still the same. That's a guarantee by the FreeBSD project. Or in other words, binary compatibility between all 8.x releases (or all 7.x, or whatever). So, there is no reason to update ports that is caused by using freebsd-update to do a minor version upgrade. No, you didn't need to run 'portupgrade -af' at all. Running portsnap and then 'portupgrade -a' would however have been a reasonably good idea since you were in an upgrading mood. Ports may well have become out of date due to the normal updating of the ports tree over the passage of time. This is largely independent of development schedules in the base system, so should there can be updates available to apply at just about any time. On the other hand, if you do a *major* version upgrade, you simply *do* need to reinstall every port. freebsd-update warns you about this directly, and the necessity of doing so is well documented all over the place eg. at Colin Percival's blog: http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.= html Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig6457A5B2001872FE63BC22CC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxJ+YgACgkQ8Mjk52CukIyu3gCeKhI0WZiNC9997VjtgO22zPNo rtsAn3TG/6UbcnsabfuDri3KU+HIxXPP =XCJa -----END PGP SIGNATURE----- --------------enig6457A5B2001872FE63BC22CC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C49F980.8060008>