bpkg-pkg-uninstall(1)

πŸ“¦
version 0.17.0 Β· 2 versions
, in fedora 43, fedora 44, nixos 26.05

πŸ’… bpkg-pkg-uninstall β€” the "okay we're DONE here" command

hey bestie 🫢 welcome to the bpkg-pkg-uninstall(1) page from the General Commands Manual β€” yes that's the whole vibe, it's a manual page, and it's about uninstalling stuff. sometimes you gotta let things go ✨


🌸 NAME 🌸

bpkg-pkg-uninstall β€” uninstall package. that's it. that's the name. iconic brevity.


πŸŽ€ SYNOPSIS πŸŽ€

bpkg pkg-uninstall|uninstall [options] [vars] pkg...
bpkg pkg-uninstall|uninstall [options] [vars] --all|-a
bpkg pkg-uninstall|uninstall [options] [vars] (--all-pattern
<pattern>)...

three whole forms, pick your fighter πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so listen. the pkg-uninstall command uninstalls the packages you name. depending on which form you use:

  • first form β€” uninstalls the specified packages, periodt.
  • second form β€” uninstalls all the held packages (peep bpkg-pkg-status(1) for what "held" even means, iykyk).
  • third form β€” uninstalls all the held packages that match any of the wildcard patterns you gave it.

and like, you can also take out the dependencies while you're at it β€” immediate ones or all of them β€” by passing --immediate|-i or --recursive|-r respectively. slay.

underneath all the cute vibes, this command literally doesn't do much more than run b uninstall. that's the whole tea β˜•. important though: in the first form, the packages you name must have been previously configured with bpkg-pkg-build(1) or bpkg-pkg-configure(1). no configuring, no uninstalling, no exceptions, sorry babe 😭

you can also pass extra command line variables (vars, normally config.*) through to the build system. those variables apply to all the specified packages, but you can also scope them to only specific packages using the argument grouping mechanism β€” see bpkg-argument-grouping(1) for the deets, and bpkg-pkg-install(1) if you want actual examples. the way that grouping works is genuinely so useful bestie, fr fr πŸ’œ


✨ PKG-UNINSTALL OPTIONS ✨

  • --all, -a β€” uninstall all the held packages. everything. gone. goodbye πŸ‘‹
  • --all-pattern pattern β€” uninstall held packages that match the specified wildcard pattern. repeat this option to match multiple patterns. > heads up: you may need to quote the pattern so your shell doesn't expand it before bpkg even sees it πŸ™ˆ
  • --immediate, -i β€” also uninstall immediate dependencies.
  • --recursive, -r β€” also uninstall all dependencies, recursively. the full cascade, no survivors πŸ”₯
  • --directory, -d dir β€” assume the configuration is in dir instead of in the current working directory.

🌈 COMMON OPTIONS 🌈

these are the shared ones β€” here's the summary, and if you want the full essay there's a more detailed description waiting in bpkg-common-options(1) πŸ’–

  • -v β€” print the essential underlying commands being executed.
  • -V β€” print all the underlying commands being executed. every last one.
  • --quiet, -q β€” run quietly, only printing error messages. silent mode activated 🀫
  • --verbose level β€” set the diagnostics verbosity to level, somewhere between 0 and 6.
  • --stdout-format format β€” the representation format to use when printing to stdout.
  • --jobs, -j num β€” number of jobs to perform in parallel.
  • --no-result β€” don't print informational messages about the outcome of performing a command or some of its parts. no little victory lap messages for you.
  • --structured-result fmt β€” write the result of performing a command in a structured form.
  • --progress β€” display progress indicators for long-lasting operations, like network transfers, building, etc.
  • --no-progress β€” suppress progress indicators for long-lasting operations, like network transfers, building, etc.
  • --diag-color β€” use color in diagnostics. aesthetic diagnostics, we love to see it 🌈
  • --no-diag-color β€” don't use color in diagnostics.
  • --build path β€” the build program to be used to build packages.
  • --build-option opt β€” additional option to be passed to the build program.
  • --fetch path β€” the fetch program to be used to download resources.
  • --fetch-option opt β€” additional option to be passed to the fetch program.
  • --fetch-timeout sec β€” the fetch and fetch-like (for example, git) program timeout.
  • --pkg-proxy url β€” HTTP proxy server to use when fetching package manifests and archives from remote pkg repositories.
  • --git path β€” the git program to be used to fetch git repositories.
  • --git-option opt β€” additional common option to be passed to the git program.
  • --sha256 path β€” the sha256 program to be used to calculate SHA256 sums.
  • --sha256-option opt β€” additional option to be passed to the sha256 program.
  • --tar path β€” the tar program to be used to extract package archives.
  • --tar-option opt β€” additional option to be passed to the tar program.
  • --openssl path β€” the openssl program to be used for crypto operations.
  • --openssl-option opt β€” additional option to be passed to the openssl program.
  • --auth type β€” types of repositories to authenticate.
  • --trust fingerprint β€” trust repository certificate with a SHA256 fingerprint.
  • --trust-yes β€” assume the answer to all authentication prompts is yes.
  • --trust-no β€” assume the answer to all authentication prompts is no.
  • --git-capabilities up=pc β€” protocol capabilities (pc) for a git repository URL prefix (up).
  • --pager path β€” the pager program to be used to show long text.
  • --pager-option opt β€” additional option to be passed to the pager program.
  • --options-file file β€” read additional options from file.
  • --default-options dir β€” the directory to load additional default options files from.
  • --no-default-options β€” don't load default options files.
  • --keep-tmp β€” don't remove bpkg's temporary directory at the end of the command execution, and print its path at verbosity level 2 or higher.

🧚 DEFAULT OPTIONS FILES 🧚

want the big picture on how default options files work? it's all in bpkg-default-options-files(1) β€” go look, bestie 🫢

for the pkg-uninstall command specifically, the search start directory is the configuration directory. in each directory, bpkg goes looking for the following options files and, if it finds them, loads them in exactly this order:

bpkg.options
bpkg-pkg-uninstall.options
⚠️ and these pkg-uninstall command options cannot be specified in the default options files, so don't even try: --directory|-d

πŸ’€ BUGS πŸ’€

found a bug? send those bug reports to the users@build2.org mailing list. they wanna hear it, promise πŸ’Œ


Copyright (c) 2014-2024 the build2 authors.

Permission is granted to copy, distribute and/or modify this document under the terms of the MIT License.


okay that's the whole page, you made it to the end, so proud of you πŸ₯ΉπŸŒΈ this was bpkg-pkg-uninstall(1) from bpkg 0.17.0, dated June 2024 β€” go forth and uninstall responsibly, bestie πŸ’–βœ¨πŸ‘‘

πŸ“¦ where this page comes from