Date: Sat, 20 Dec 2025 17:02:23 -0800 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD-pkgbase@freebsd.org, FreeBSD-pkg@freebsd.org Subject: man pkg-unregister synopsis for -a vs. --all; more Message-ID: <20DAA4A9-B47A-4551-8EE0-E245D63D902F@yahoo.com> References: <20DAA4A9-B47A-4551-8EE0-E245D63D902F.ref@yahoo.com>
index | next in thread | previous in thread | raw e-mail
pkg unregister [-Dnqy] -a
. . .
pkg unregister [--{dry-run,quiet,yes}] --all
. . .
-D, --no-scripts
If a deinstallation script exists for a given package, do not
execute it.
One form indicates it an an option and the other
does not.
Also:
pkg related man pages do not seem to reference
the pkg-unregister page.
pkg unregister -n . . . seems to always list all,
even pkg, not showing what would actually match
based on the various examples I tried (replacing
". . ." above).
The -n output reported in my context:
QUOTE
The following package(s) are locked or vital and may not be removed:
FreeBSD-clibs (vital)
FreeBSD-runtime (vital)
FreeBSD-set-base (vital)
FreeBSD-set-base-jail (vital)
FreeBSD-set-devel (vital)
FreeBSD-set-lib32 (vital)
FreeBSD-set-minimal (vital)
FreeBSD-set-minimal-jail (vital)
FreeBSD-set-optional (vital)
FreeBSD-set-optional-jail (vital)
FreeBSD-set-src (vital)
FreeBSD-set-tests (vital)
END QUOTE
So I'm not sure if such would end up unregistered
or not.
The -n output had lots of solver messages.
(I looked at this stuff because I was trying to help
with someone's questions about getting an accidental
pkgbase install to no longer be pkgbase. I could not
be of much help with that at this point. The context
involved attempting a system recovery from a messed
up non-pkgbase system and that ended up with the
pkgbase system install before I was involved.)
===
Mark Millard
marklmi at yahoo.com
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20DAA4A9-B47A-4551-8EE0-E245D63D902F>