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> In-Reply-To: <0fbe4e76-f482-c936-7bf2-2b689d6902d2@yandex.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180511164634.GA19106>