Date: Tue, 26 Aug 2025 23:09:32 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-pkgbase@freebsd.org Cc: re@freebsd.org Subject: pkg upgrade (was: freebsd-update and pkgbase) Message-ID: <dfc2de28-f496-4746-ac78-5b5ff68c5ed6@gmail.com> In-Reply-To: <39020a5b-a218-43d3-8c9c-945787c74561@quip.cz> References: <aJPGX9zXE3MeiuhP@nuc> <aKSgDAqct9o1MiNZ@nuc> <20250820011537.7a3ccb3e@nuclight.lan> <39020a5b-a218-43d3-8c9c-945787c74561@quip.cz>
index | next in thread | previous in thread | raw e-mail
Baptiste's presentation a decade ago, before my time, included the end user perspective for upgrading the system: pkg upgrade Subject lines of the January 2016 update, and the March call for testing included: pkg(8) – and the install command was for installation. I imagined nothing other than the upgrade command for upgrading. Approaches that are coherent are highly valued. pkgbase, as originally intended, can be embraced. Packages, tools, and conventions; with 'pkg upgrade' naturally amongst the conventions. <https://www.bsdcan.org/2015/schedule/attachments/321_packaging-base.pdf#page=26>; <https://lists.freebsd.org/pipermail/freebsd-pkgbase/2016-January/000000.html>, first sentence: > … package and upgrade the FreeBSD base system using pkg(8). <https://lists.freebsd.org/pipermail/freebsd-pkgbase/2016-March/000032.html>;help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dfc2de28-f496-4746-ac78-5b5ff68c5ed6>