From owner-freebsd-questions@freebsd.org  Fri May 11 16:51:56 2018
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92DA6FAA798
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Fri, 11 May 2018 16:51:56 +0000 (UTC)
 (envelope-from merlyn@geeks.org)
Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3B17F7512C
 for <freebsd-questions@freebsd.org>; Fri, 11 May 2018 16:51:56 +0000 (UTC)
 (envelope-from merlyn@geeks.org)
Received: from mail.geeks.org (localhost [127.0.0.1])
 by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 997A1110219
 for <freebsd-questions@freebsd.org>; Fri, 11 May 2018 11:46:34 -0500 (CDT)
Received: by mail.geeks.org (Postfix, from userid 1003)
 id 7A38311020B; Fri, 11 May 2018 11:46:34 -0500 (CDT)
Date: Fri, 11 May 2018 11:46:34 -0500
From: Doug McIntyre <merlyn@geeks.org>
To: freebsd-questions@freebsd.org
Subject: Re: A request for release engineering
Message-ID: <20180511164634.GA19106@geeks.org>
References: <4acac175-9bf2-40a6-a41a-cb5870641c8d@yandex.com>
 <670715be-849c-47fc-72b4-42b81cf31c0a@qeng-ho.org>
 <DFED4A6E-BC93-4D62-AD86-A441BDB2BD8E@sigsegv.be>
 <alpine.BSF.2.20.1805110708180.38383@beak.h.net>
 <0fbe4e76-f482-c936-7bf2-2b689d6902d2@yandex.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0fbe4e76-f482-c936-7bf2-2b689d6902d2@yandex.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-Virus-Scanned: ClamAV using ClamSMTP
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 16:51:56 -0000

On Fri, May 11, 2018 at 08:10:14PM +0530, Manish Jain wrote:
> Since bumping the version up using freebsd-update needs you to install 
> all packages afresh, it would appear to my naked eye that it never makes 
> sense to upgrade. Instead, one should simply wait till one's release 
> version goes beyond EOL - and then install the latest available release 
> afresh. This is just what I plan on this box (10.3) - wait till 
> November, and then install 12 over the current installation.


Do people not generally use binary pkg's?

pkg upgrade

generally works fine as part of a 10.3->11.1 (or 10.3->11.0) freebsd-update path.
It'll automatically uninstall and reinstall the new ABI version packages for you.

Granted, my scale makes my local poudriere build server nice, but I
don't have that many customizations to my source builds that stock
binary builds would work for 98% of my package set.

I couldn't imagine rebuilding kernel/packages from ports source as
part of every upgrade cycle. My primary home server works just fine
with binary updates, binary pkg updates on everything I do there.