bpkg-pkg-update(1)

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

πŸ’– bpkg-pkg-update β€” the bpkg-pkg-update(1) glow-up ✨

okay bestie, welcome to the General Commands Manual section of the bpkg cinematic universe πŸŽ€ this one's called bpkg-pkg-update and it does exactly what it says on the tin: it updates packages. iconic behavior honestly.


🌸 NAME 🌸

bpkg-pkg-update β€” update package πŸ¦‹


⭐ SYNOPSIS ⭐

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

πŸ’… DESCRIPTION πŸ’…

so like, pkg-update updates the packages you name (that's form one), or all the held packages (form two β€” peep bpkg-pkg-status(1) for the deets on what "held" even means), or all the held packages that match any of the wildcard patterns you throw at it (form three). and yes, you can also drag the dependencies along for the ride: hit it with --immediate|-i for the immediate ones, or --recursive|-r for all of them, recursively, no cap πŸ”₯

under the hood it's not doing some wild sorcery β€” it's basically just running b update (or one of its update-for-* variants; see --for|-f). 🫢 in that first form, the packages you specify must have already been configured with bpkg-pkg-build(1) or bpkg-pkg-configure(1). no skipping steps, babes.

extra command line variables (vars, usually config.*) can be passed straight to the build system ✨ those variables apply to all the specified packages, but you can also scope them so they only apply to specific packages using the argument grouping mechanism β€” go read bpkg-argument-grouping(1) for the full tea πŸ’œ


πŸŽ€ PKG-UPDATE OPTIONS πŸŽ€

  • --all|-a β€” update all held packages. every single one. the whole squad. πŸ‘‘
  • --all-pattern pattern β€” update the held packages that match the wildcard pattern. repeat this option to match multiple patterns, queen 🌈 heads up tho: you may need to quote the pattern so your shell doesn't expand it before bpkg even sees it 😭
  • --immediate|-i β€” also update immediate dependencies 🧚
  • --recursive|-r β€” also update all dependencies, recursively. down the whole tree, we go πŸ’€
  • --for|-f operation β€” instead of the default update build system operation, do the update-for-operation variant, where operation is normally install or test ⭐
  • --directory|-d dir β€” assume the configuration is in dir rather than in the current working directory πŸ“

🌈 COMMON OPTIONS 🌈

these are the shared ones β€” the full-length director's cut lives in bpkg-common-options(1) πŸ“–

  • -v β€” print the essential underlying commands being executed.
  • -V β€” print all the underlying commands being executed. every last one. we're nosy today πŸ™ˆ
  • --quiet|-q β€” run quietly, only printing error messages 🀫
  • --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 β€” how many jobs to perform in parallel. multitasking queen πŸ‘‘
  • --no-result β€” don't print informational messages about the outcome of performing a command or some of its parts.
  • --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 those progress indicators for long-lasting operations, like network transfers, building, etc.
  • --diag-color β€” use color in diagnostics 🌸
  • --no-diag-color β€” don't use color in diagnostics.
  • --build path β€” the build program to be used to build packages.
  • --build-option opt β€” an additional option to pass to the build program.
  • --fetch path β€” the fetch program to be used to download resources.
  • --fetch-option opt β€” an additional option to pass to the fetch program.
  • --fetch-timeout sec β€” the fetch and fetch-like (for example, git) program timeout ⏰
  • --pkg-proxy url β€” the 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 β€” an additional common option to pass to the git program.
  • --sha256 path β€” the sha256 program to be used to calculate SHA256 sums πŸ”
  • --sha256-option opt β€” an additional option to pass to the sha256 program.
  • --tar path β€” the tar program to be used to extract package archives.
  • --tar-option opt β€” an additional option to pass to the tar program.
  • --openssl path β€” the openssl program to be used for crypto operations πŸ”’
  • --openssl-option opt β€” an additional option to pass to the openssl program.
  • --auth type β€” the types of repositories to authenticate.
  • --trust fingerprint β€” trust a 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 β€” an additional option to pass 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, periodt.
  • --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. lil souvenir 🎁

🧚 DEFAULT OPTIONS FILES 🧚

peep bpkg-default-options-files(1) for the big-picture overview of default options files πŸ’œ

for the pkg-update command, the search start directory is the configuration directory. the following options files are searched for in each directory and, if found, loaded in the order listed:

bpkg.options
bpkg-pkg-update.options

and these pkg-update command options cannot be specified in the default options files, bestie:

--directory|-d

πŸ’€ BUGS πŸ’€

found a bug? send bug reports to the users@build2.org mailing list πŸ“¬


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. slay πŸ’–


and that's the whole page, babe β€” this was bpkg-pkg-update(1) from bpkg 0.17.0, dated June 2024. mwah, go update something πŸ’…βœ¨

πŸ“¦ where this page comes from