On 8/6/2025 1:40 PM, vermaden wrote:
Because that’s what you asked for.
Why would the command do anything other than that?
If it did not, what command should and would you oppose it existing?
The problem is that the same 'pkg delete -af' command - will behave DIFFERENTLY
with PKGBASE and without PKGBASE on the same FreeBSD version system - that is
the center of the problem.
Everyone that use FreeBSD got used to the fact that pkg(8) command maintains
only third party packages and Base System is untouched. With current state of
PKGBASE FreeBSD is no different then a Linux distribution with yum/dnf/apt
package manager - the Base System 'security' is broken
The suggestion re the addition of "pkgbase" command, using its own
configuration files, is the best, most straightforward, fix for those
of us who have qualms with the current implementation. The back-end
stuff doesn't really need to change as far as I can see. But keeping the
base separated is paramount.
If for some reason that is beyond the pale, another solution would be to
add a new directive to the repository configuration syntax that allows
us to exclude a given repo from the pkg default actions. Something like
'OnlyWhenSpecified: "yes"' or 'ExcludeFromDefaults: "yes"'. Terrible
names but I expect something better could be found. The effect should be
that the given repo is only operated on when the -R argument calls for
the associated repo directly. So "pkg upgrade" would operate on all
repos except the repos that have that setting. Think of it as an
'ENABLED' but with restrictions.
The exclusion should be the default for the config that's being tagged
as FreeBSD-base.
