bpkg-pkg-configure(1) General Commands Manual bpkg-pkg-configure(1)

bpkg-pkg-configure - configure package

bpkg pkg-configure [options] [cfg-var...] pkg

The pkg-configure command configures either the previously unpacked (bpkg-pkg-unpack(1), bpkg-pkg-checkout(1)) source code package or a package that is present in the system.

A source code package inherits the common build2 configuration values that were specified when creating the configuration (bpkg-cfg-create(1)). Additional package-specific configuration variables can be passed to pkg-configure (cfg-var).

A system package is specified using the sys:pkg[/ver] syntax. If the package version (ver) is not specified, then it is considered to be unknown but satisfying any dependency constraint. Such a version is displayed as *.

Assume configuration is in dir rather than in the current working directory.

The common options are summarized below with a more detailed description available in bpkg-common-options(1).

Print essential underlying commands being executed.
Print all underlying commands being executed.
Run quietly, only printing error messages.
Set the diagnostics verbosity to level between 0 and 6.
Representation format to use for printing to stdout.
Number of jobs to perform in parallel.
Don't print informational messages about the outcome of performing a command or some of its parts.
Write the result of performing a command in a structured form.
Display progress indicators for long-lasting operations, such as network transfers, building, etc.
Suppress progress indicators for long-lasting operations, such as network transfers, building, etc.
Use color in diagnostics.
Don't use color in diagnostics.
The build program to be used to build packages.
Additional option to be passed to the build program.
The fetch program to be used to download resources.
Additional option to be passed to the fetch program.
The fetch and fetch-like (for example, git) program timeout.
HTTP proxy server to use when fetching package manifests and archives from remote pkg repositories.
The git program to be used to fetch git repositories.
Additional common option to be passed to the git program.
The sha256 program to be used to calculate SHA256 sums.
Additional option to be passed to the sha256 program.
The tar program to be used to extract package archives.
Additional option to be passed to the tar program.
The openssl program to be used for crypto operations.
Additional option to be passed to the openssl program.
Types of repositories to authenticate.
Trust repository certificate with a SHA256 fingerprint.
Assume the answer to all authentication prompts is yes.
Assume the answer to all authentication prompts is no.
Protocol capabilities (pc) for a git repository URL prefix (up).
The pager program to be used to show long text.
Additional option to be passed to the pager program.
Read additional options from file.
The directory to load additional default options files from.
Don't load default options files.
Don't remove the bpkg's temporary directory at the end of the command execution and print its path at the verbosity level 2 or higher.

See bpkg-default-options-files(1) for an overview of the default options files. For the pkg-configure 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-configure.options

The following pkg-configure command options cannot be specified in the default options files:

--directory|-d

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.

June 2024 bpkg 0.17.0