1bpkg-pkg-update(1) General Commands Manual bpkg-pkg-update(1)
2
6 bpkg-pkg-update - update package
7
9 bpkg pkg-update|update [options] [vars] pkg...
10 bpkg pkg-update|update [options] [vars] --all|-a
11 bpkg pkg-update|update [options] [vars] (--all-pattern <pattern>)...
12
14 The pkg-update command updates the specified packages (the first form),
15 all the held packages (the second form, see bpkg-pkg-status(1)), or all
16 the held packages that match any of the specified wildcard patterns
17 (the third form). Additionally, immediate or all dependencies of these
18 packages can be also updated by specifying the --immediate|-i or --re‐
19 cursive|-r options, respectively. Underneath, this command doesn't do
20 much more than run b update (or one of its update-for-* variants; see
21 --for|-f). In the first form the specified packages must have been pre‐
22 viously configured with bpkg-pkg-build(1) or bpkg-pkg-configure(1).
23 Additional command line variables (vars, normally config.*) can be
25 passed to the build system. Such variables apply to all the specified
26 packages but can also be specified to only apply to specific packages
27 using the argument grouping mechanism (see bpkg-argument-grouping(1)
28 for details).
29
31 --all|-a
32 Update all held packages.
33 --all-pattern pattern
35 Update held packages that match the specified wildcard pattern.
36 Repeat this option to match multiple patterns. Note that you may
37 need to quote the pattern to prevent expansion by your shell.
38 --immediate|-i
40 Also update immediate dependencies.
41 --recursive|-r
43 Also update all dependencies, recursively.
44 --for|-f operation
46 Instead of the default update build system operation, perform
47 the update-for-operation variant where operation is normally in‐
48 stall or test.
49 --directory|-d dir
51 Assume configuration is in dir rather than in the current work‐
52 ing directory.
53
55 The common options are summarized below with a more detailed descrip‐
56 tion available in bpkg-common-options(1).
57 -v Print essential underlying commands being executed.
59 -V Print all underlying commands being executed.
61 --quiet|-q
63 Run quietly, only printing error messages.
64 --verbose level
66 Set the diagnostics verbosity to level between 0 and 6.
67 --stdout-format format
69 Representation format to use for printing to stdout.
70 --jobs|-j num
72 Number of jobs to perform in parallel.
73 --no-result
75 Don't print informational messages about the outcome of perform‐
76 ing a command or some of its parts.
77 --structured-result fmt
79 Write the result of performing a command in a structured form.
80 --progress
82 Display progress indicators for long-lasting operations, such as
83 network transfers, building, etc.
84 --no-progress
86 Suppress progress indicators for long-lasting operations, such
87 as network transfers, building, etc.
88 --diag-color
90 Use color in diagnostics.
91 --no-diag-color
93 Don't use color in diagnostics.
94 --build path
96 The build program to be used to build packages.
97 --build-option opt
99 Additional option to be passed to the build program.
100 --fetch path
102 The fetch program to be used to download resources.
103 --fetch-option opt
105 Additional option to be passed to the fetch program.
106 --fetch-timeout sec
108 The fetch and fetch-like (for example, git) program timeout.
109 --pkg-proxy url
111 HTTP proxy server to use when fetching package manifests and ar‐
112 chives from remote pkg repositories.
113 --git path
115 The git program to be used to fetch git repositories.
116 --git-option opt
118 Additional common option to be passed to the git program.
119 --sha256 path
121 The sha256 program to be used to calculate SHA256 sums.
122 --sha256-option opt
124 Additional option to be passed to the sha256 program.
125 --tar path
127 The tar program to be used to extract package archives.
128 --tar-option opt
130 Additional option to be passed to the tar program.
131 --openssl path
133 The openssl program to be used for crypto operations.
134 --openssl-option opt
136 Additional option to be passed to the openssl program.
137 --auth type
139 Types of repositories to authenticate.
140 --trust fingerprint
142 Trust repository certificate with a SHA256 fingerprint.
143 --trust-yes
145 Assume the answer to all authentication prompts is yes.
146 --trust-no
148 Assume the answer to all authentication prompts is no.
149 --git-capabilities up=pc
151 Protocol capabilities (pc) for a git repository URL prefix (up).
152 --pager path
154 The pager program to be used to show long text.
155 --pager-option opt
157 Additional option to be passed to the pager program.
158 --options-file file
160 Read additional options from file.
161 --default-options dir
163 The directory to load additional default options files from.
164 --no-default-options
166 Don't load default options files.
167 --keep-tmp
169 Don't remove the bpkg's temporary directory at the end of the
170 command execution and print its path at the verbosity level 2 or
171 higher.
172
174 See bpkg-default-options-files(1) for an overview of the default op‐
175 tions files. For the pkg-update command the search start directory is
176 the configuration directory. The following options files are searched
177 for in each directory and, if found, loaded in the order listed:
178 bpkg.options
180 bpkg-pkg-update.options
181 The following pkg-update command options cannot be specified in the de‐
183 fault options files:
184 --directory|-d
186
188 Send bug reports to the users@build2.org mailing list.
189
191 Copyright (c) 2014-2023 the build2 authors.
192 Permission is granted to copy, distribute and/or modify this document
194 under the terms of the MIT License.
195bpkg 0.16.0 June 2023 bpkg-pkg-update(1)