NAME

bpkg-cfg-add – associate configuration

SYNOPSIS

bpkg cfg-add [options] dir

DESCRIPTION

The cfg-add command associates the current bpkg configuration with the specified configuration, so that dependencies of a package built in the current configuration can be built in associated, potentially shared configurations.

The associated configurations are referred by name or identifier when specified on the bpkg command line. The original configuration name can we overridden by specifying the --name option.

If the specified directory path is relative, then its path is rebased against the current configuration directory path before being saved. This way the associated configurations can be moved around together with the relative locations preserved. If the directory path is absolute then it is just normalized before being saved, unless the --relative option is specified.

CFG-ADD OPTIONS

--name|-n name
Override the associated configuration name.
--relative
Rebase the associated configuration directory absolute path against the current configuration directory path, in the same way as for the relative paths. Has no effect on relative paths.
--directory|-d dir
Assume configuration is in dir rather than in the current working directory.

COMMON OPTIONS

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

-v
Print essential underlying commands being executed.
-V
Print all underlying commands being executed.
--quiet|-q
Run quietly, only printing error messages.
--verbose level
Set the diagnostics verbosity to level between 0 and 6.
--jobs|-j num
Number of jobs to perform in parallel.
--no-result
Don't print informational messages about the outcome of performing a command.
--no-progress
Suppress progress indicators for long-lasting operations, such as network transfers, building, etc.
--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.
--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.

DEFAULT OPTIONS FILES

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

The following cfg-add command options cannot be specified in the default options files:

--directory|-d

BUGS

Send bug reports to the users@build2.org mailing list.