Date: Sat, 25 Aug 2012 04:55:48 +0100 From: Ben Morrow <ben@morrow.me.uk> To: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.1-RC1 Available... Message-ID: <20120825035543.GA25767@anubis.morrow.me.uk> In-Reply-To: <1345729674.52121.4.camel@bauer.cse.buffalo.edu> References: <1345697446.84337.11.camel@neo.cse.buffalo.edu> <20120823225855.U33776@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoth Ken Smith <kensmith@buffalo.edu>: > > The latter. If you are not using FreeBSD-Update to handle the updates > of a machine you'll need to update your source tree using SVN for > release branches (releng/*) from now on. Updates of the CVS repository > will continue for the existing stable/* and head for now. I don't think > anything has been decided on when that will stop. Two questions: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. 2. If I have patched my source tree, what will freebsd-update do? csup resets the patched files to the versions in the new tree, which is satisfactory (I can reapply any patches afterwards, adjusting them if necessary), but if freebsd-update leaves a mixture of new-and-unpatched and old-and-patched files in the tree that could be a problem. (Not an insoluble problem, of course, especially with ZFS snapshots.) Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120825035543.GA25767>