Date: Mon, 12 Nov 2007 10:06:50 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Colin Percival <cperciva@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc freebsd-update.conf src/share/man/man5 freebsd-update.conf.5 src/usr.sbin/freebsd-update freebsd-update.8 freebsd-update.sh Message-ID: <86r6ivj0id.fsf@ds4.des.no> In-Reply-To: <200711120447.lAC4lwua029042@repoman.freebsd.org> (Colin Percival's message of "Mon\, 12 Nov 2007 04\:47\:58 %2B0000 \(UTC\)") References: <200711120447.lAC4lwua029042@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Colin Percival <cperciva@FreeBSD.org> writes: > Log: > Add support for "freebsd-update -r newrelease upgrade" -- binary > upgrading to new releases. Important parts of this code include > * automatically determining which optional components (e.g., src, > info, proflibs) are installed. > * merging changes in files which are modified locally and have > changed between the currently running and new release. > * prompting the user to rebuild all 3rd party software before > deleting old shared libraries. So, let's say you have a 6.2 box (predating this change) and want to update to 6.3, what would the procedure be? Install a newer freebsd-update from ports? Or will the newer freebsd-update be distributed as a binary update for older releases? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86r6ivj0id.fsf>