From owner-freebsd-current@FreeBSD.ORG Mon May 11 00:29:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 984AD106566C for ; Mon, 11 May 2009 00:29:40 +0000 (UTC) (envelope-from jdl@jdl.com) Received: from jdl.com (jdl.com [208.123.74.7]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8AB8FC1A for ; Mon, 11 May 2009 00:29:40 +0000 (UTC) (envelope-from jdl@jdl.com) Received: from jdl (helo=jdl.com) by jdl.com with local-esmtp (Exim 4.69) (envelope-from ) id 1M3JOk-0007fX-CH; Sun, 10 May 2009 19:29:38 -0500 To: Giorgos Keramidas In-reply-to: <87vdo8powi.fsf@kobe.laptop> References: <87vdo8powi.fsf@kobe.laptop> Comments: In-reply-to Giorgos Keramidas message dated "Mon, 11 May 2009 01:35:25 +0300." Date: Sun, 10 May 2009 19:29:38 -0500 From: Jon Loeliger Message-Id: X-Spam-Score: -2.3 Cc: freebsd-current@freebsd.org Subject: Re: Feedback and Questions Updating to CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2009 00:29:40 -0000 Hi Giorgos, Thanks for your help here! > You are right that there is a fair bit of improvement we could make to > the 'make world from scratch' chapter. I've thought a bit about this > and I think we need to split this in at least a few more parts: > > - How to update from X.0-RELEASE to a newer Y.0-RELEASE. > > - How to upgrade from X.0-RELEASE to RELENG_X (for security updates > only). > > - How to upgrade across major releases (from X.0-RELEASE to some > newer Y.0-RELEASE or later code). > > - How to upgrade from X-STABLE to Y-CURRENT. > > There is inevitably some amount of repetition in these four upgrade > procedures, but it may be more intuitive to have *all* the steps for > each one of them in a consecutive section. > > If that sounds like something that would simplify things and make the > upgrade steps more useful, please help us organize the documentation to > match a better shape by posting any ideas to freebsd-doc. That wasn't the issue for me. My confusion stemmed from the fact that it was the *same* material just repeated 3 times. By the time I had read hrough the first set, I was baffled to stumble onto the second and third set. I think that if early in the page it had said something like Here's the overview of the steps we'll take:... In the next section, we'll progress through each of these steps in more detail... > If you upgrade from 7.X-RELEASE to CURRENT it is probably a good idea to > rebuild all ports with: Check. I found the Handbook chapter that covered this. It's all coming back to me slowly... > pkgdb -Fu && portupgrade -fa > > or: > > portmaster -fa And confusingly here, there's no indication as to why I might pick one or the other, nor the pros and cons of either, nor if having picked one, I could use the other later. So I set the first of those commands into motion and went to dinner. I was totally frustrated to find that some potentially large portion of that time was wasted waiting for an interactive response to some question that had a single-already-checked question that just needed to be confirmed or unchecked. Hrm. A "use the defaults" configuration for totally non-interactive build would have been my expectation here. Will I need to babysit this whole build now? Yep. > Every time you `portsnap fetch' and `portsnap update' you should look at > `/usr/ports/UPDATING' too. Some the `UPDATING' file lists important > upgrade steps that have to be performed manually. That's the one thing that's been clear so far. :-) jdl