Re: pkgbase update procedure, using, for example, clibs as an example to illustrate the more general question

On Sep 12, 2025, at 17:19, Mark Millard <marklmi@yahoo.com> wrote:

> Context: native hardware, not jails and such.

More implicit context that drove the question: this was
checking on what to do for my "main" (or stable/*) based
contexts, not for Release to Release Update procedures.
Various types of issues happen more on main as it
progresses.

> Is the appropriate general order for updates based on pkgbase
> still based on to be used kernel (and possibly related files,
> such as dtb files) being installed first --and rebooting
> before other things are installed?
> 
> Those wanted: FreeBSD-kernel-generic* (as in the "kernels" "set")
> If involved:  FreeBSD-dtb             (as in the "minimal" "set")
> Possibly:     FreeBSD-bootloader      (as in the "minimal" "set")
> (U-Boot or other such things from outside FreeBSD may also be
> involved here.)
> 
> Then: reboot
> 
> So: even the "vital" packages wait until after that reboot
> into a new kernel before they are installed? :
> 
> The "vital" base packages:
> FreeBSD-clibs   (as in the minimal "set")
> FreeBSD-runtime (as in the minimal "set")
> 
> (From here on omitting that level of detail but still being
> somewhat suggestive.)
> 
> The "minimal" "set" overall, for things not indicated above
> 
> Things wanted from:
> The "base" "set" overall,    for things not indicated above
> 
> Things wanted from (probably all or nothing):
> The "lib32" "set" overall.
> 
> Things wanted from:
> The "devel" "set" overall.
> 
> Things wanted from:
> Anything existing that is not in one of those "sets".
> 
> Then: reboot get get system operation that is based just
>      on the update.
> 
> 
> Note:
> 
> I've not tried to document here updates related to
> *.pkgsave or *.pkgnew or .pkgtemp.* files.
> 
> Nor have I been explicit about *-dbg packages.
> 
> I also ignore updating port-packages above.


===
Mark Millard
marklmi at yahoo.com