> On 9 Dec 2025, at 16:47, Lexi Winter <[email protected]> wrote:
>
> Peter Ankerstål wrote in <[email protected]>:
>>
>
> the only exception to this is if you install a package set, such as
> FreeBSD-set-minimal, and new packages are added to that set; in that
> case the new packages will be installed. if you want to avoid that,
> you can simply not install (or remove) the set package. after doing
> that, make sure to mark all the existing packages as not automatically
> installed, otherwise pkg autoremove might remove them.
Thanks! Of course its the sets that trigger this behavior. I didnt realize
that, but yeah, I guess removing the meta package after installation will solve
this problem.
>
>> A side track for this question is security updates. Using 14.3
>> upgrading to a new patch level pkg upgraded all installed FreeBSD-base
>> packages at the new patch level. Why couldn’t it just install the
>> packages that changed with that patch level?
>
> i am not sure i understand what you're asking here; could you please
> provide an example of the behaviour you're talking about, and also
> describe how you think it should work instead?
When using freebsd-update and there is a new patchlevel only the affected files
are updated. Lets say the patchlevel only contains a fix for unbound. Then
freebsd-update will only download and install unbound-files.
But when moving from one patchlevel to another using pkgbase all installed
packages from FreeBSD-base will be updated. But it would have been enough to
just upgrade the FreeBSD-unbound package.
/Peter.
