On May 11, 2025, at 08:33, Baptiste Daroussin <b...@freebsd.org> wrote:
> Le 11 mai 2025 17:29:49 GMT+02:00, Mark Millard <mark...@yahoo.com> a écrit : >> In a system/chroot that is based on PkgBase, a "pkg delete -a" >> that is allowed to run also destroys the system software, not >> just port packages. There is no way to delete just all the >> port packages in a PkgBase based system as far as I can tell. >> >> >> === >> Mark Millard >> marklmi at yahoo.com >> > > no! > > there is a vital flag set on some packages that should prevent the bare > minimal to be removed > without -f Sounds like the vital flag is supposed to preserve enough that ports-mgmt/pkg and the system pkg are supposed to be fully operational? Also: ports package uninstaller and installer activity that the usage could lead to? As I remember the "pkg delete -a" gots lots of uninstall script errors from not following a dependency order that would be required for such things to be kept fully working during the delete sequence. Also, might it only be pkg-static that is to stay operational? At some point I'll have to retry my experiment: As I remember last I tried pkg itself was broken via lack of a library and I had to use pkg-static. (This can be an issue for any scripts or such not coded to use pkg-static.) But my last experiment might not have been recent enough to be reasonable. Overall: how to I know if some behavior after "pkg delete -a" is something that should be reported vs. the the behavior being expected, relative to PkgBase and pkg use? === Mark Millard marklmi at yahoo.com
