From owner-cvs-src@FreeBSD.ORG Mon Nov 12 09:07:24 2007 Return-Path: Delivered-To: cvs-src@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C8D516A420; Mon, 12 Nov 2007 09:07:24 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 4D7FD13C4A3; Mon, 12 Nov 2007 09:07:24 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 2A5D92094; Mon, 12 Nov 2007 10:06:55 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id A18B32093; Mon, 12 Nov 2007 10:06:54 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 87618844AB; Mon, 12 Nov 2007 10:06:52 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Colin Percival References: <200711120447.lAC4lwua029042@repoman.freebsd.org> Date: Mon, 12 Nov 2007 10:06:50 +0100 In-Reply-To: <200711120447.lAC4lwua029042@repoman.freebsd.org> (Colin Percival's message of "Mon\, 12 Nov 2007 04\:47\:58 +0000 \(UTC\)") Message-ID: <86r6ivj0id.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2007 09:07:24 -0000 Colin Percival 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