1bpkg-cfg-link(1) General Commands Manual bpkg-cfg-link(1)
2
3
4
6 bpkg-cfg-link - link configuration
7
9 bpkg cfg-link [options] dir
10
12 The cfg-link command links the specified bpkg configuration with the
13 current configuration. Note that it also establishes an implicit back‐
14 link from the specified to the current configuration. See bpkg-cfg-cre‐
15 ate(1) for background on linked configurations. To unlink previously
16 linked configurations use bpkg-cfg-unlink(1).
17
18 The linked configurations are normally referred to using names when
19 specified on the bpkg command line. Unless overridden with the --name
20 option, the original configuration name is used to name the link. If
21 the link is unnamed, then it can be referred to using the numeric id
22 that is automatically assigned when establishing the link or using the
23 configuration UUID.
24
25 If the specified configuration path is relative, then it is rebased
26 relative to the current configuration directory. This way, when the
27 linked configurations are moved around together, the stored relative
28 paths remain valid. If the specified directory path is absolute, then
29 it is stored as absolute unless the --relative option is specified in
30 which case it is also rebased relative to the current configuration di‐
31 rectory.
32
34 --name name
35 Alternative link name. If this option is not specified, then the
36 configuration name is used as the link name (see bpkg-cfg-cre‐
37 ate(1) for details).
38
39 --relative
40 Rebase the absolute linked configuration path relative to the
41 current configuration directory.
42
43 --directory|-d dir
44 Assume configuration is in dir rather than in the current work‐
45 ing directory.
46
48 The common options are summarized below with a more detailed descrip‐
49 tion available in bpkg-common-options(1).
50
51 -v Print essential underlying commands being executed.
52
53 -V Print all underlying commands being executed.
54
55 --quiet|-q
56 Run quietly, only printing error messages.
57
58 --verbose level
59 Set the diagnostics verbosity to level between 0 and 6.
60
61 --jobs|-j num
62 Number of jobs to perform in parallel.
63
64 --no-result
65 Don't print informational messages about the outcome of perform‐
66 ing a command or some of its parts.
67
68 --no-progress
69 Suppress progress indicators for long-lasting operations, such
70 as network transfers, building, etc.
71
72 --build path
73 The build program to be used to build packages.
74
75 --build-option opt
76 Additional option to be passed to the build program.
77
78 --fetch path
79 The fetch program to be used to download resources.
80
81 --fetch-option opt
82 Additional option to be passed to the fetch program.
83
84 --fetch-timeout sec
85 The fetch and fetch-like (for example, git) program timeout.
86
87 --pkg-proxy url
88 HTTP proxy server to use when fetching package manifests and ar‐
89 chives from remote pkg repositories.
90
91 --git path
92 The git program to be used to fetch git repositories.
93
94 --git-option opt
95 Additional common option to be passed to the git program.
96
97 --sha256 path
98 The sha256 program to be used to calculate SHA256 sums.
99
100 --sha256-option opt
101 Additional option to be passed to the sha256 program.
102
103 --tar path
104 The tar program to be used to extract package archives.
105
106 --tar-option opt
107 Additional option to be passed to the tar program.
108
109 --openssl path
110 The openssl program to be used for crypto operations.
111
112 --openssl-option opt
113 Additional option to be passed to the openssl program.
114
115 --auth type
116 Types of repositories to authenticate.
117
118 --trust fingerprint
119 Trust repository certificate with a SHA256 fingerprint.
120
121 --trust-yes
122 Assume the answer to all authentication prompts is yes.
123
124 --trust-no
125 Assume the answer to all authentication prompts is no.
126
127 --pager path
128 The pager program to be used to show long text.
129
130 --pager-option opt
131 Additional option to be passed to the pager program.
132
133 --options-file file
134 Read additional options from file.
135
136 --default-options dir
137 The directory to load additional default options files from.
138
139 --no-default-options
140 Don't load default options files.
141
143 See bpkg-default-options-files(1) for an overview of the default op‐
144 tions files. For the cfg-link command the search start directory is the
145 configuration directory. The following options files are searched for
146 in each directory and, if found, loaded in the order listed:
147
148 bpkg.options
149 bpkg-cfg-link.options
150
151 The following cfg-link command options cannot be specified in the de‐
152 fault options files:
153
154 --directory|-d
155
157 Send bug reports to the users@build2.org mailing list.
158
160 Copyright (c) 2014-2021 the build2 authors.
161
162 Permission is granted to copy, distribute and/or modify this document
163 under the terms of the MIT License.
164
165
166
167bpkg 0.14.0 October 2021 bpkg-cfg-link(1)