1bdep-fetch(1) General Commands Manual bdep-fetch(1)
2
3
4
6 bdep-fetch - fetch list of available project dependencies
7
9 bdep fetch [options] [--full|-F] [prj-spec] [cfg-spec]
10
11 cfg-spec = (@cfg-name | --config|-c cfg-dir)... | --all|-a
12 prj-spec = --directory|-d prj-dir
13
15 The fetch command fetches the list of packages available in the
16 project's prerequisite/complement repositories in one or more build
17 configurations.
18
19 If no project or package directory is specified, then the current work‐
20 ing directory is assumed. If no configuration is specified, then the
21 default configurations are assumed. See bdep-projects-configs(1) for
22 details on specifying projects and configurations.
23
24 If the --full|-F option is specified, then instead fetch performs a
25 full re-fetch of all the repositories added to the configuration. This
26 mode is primarily useful when a configuration (and some of the prereq‐
27 uisite/complement repositories) are shared between several projects. In
28 this situation an incremental fetch may result in an inconsistent
29 repository state.
30
32 --full|-F
33 Perform a full re-fetch of all the repositories.
34
35 --all|-a
36 Use all build configurations.
37
38 --config|-c dir
39 Specify the build configuration as a directory.
40
41 --directory|-d dir
42 Assume project/package is in the specified directory rather than
43 in the current working directory.
44
45 --config-name|-n name
46 Specify the build configuration as a name.
47
48 --config-id num
49 Specify the build configuration as an id.
50
52 The common options are summarized below with a more detailed descrip‐
53 tion available in bdep-common-options(1).
54
55 -v Print essential underlying commands being executed.
56
57 -V Print all underlying commands being executed.
58
59 --quiet|-q
60 Run quietly, only printing error messages.
61
62 --verbose level
63 Set the diagnostics verbosity to level between 0 and 6.
64
65 --stdout-format format
66 Representation format to use for printing to stdout.
67
68 --jobs|-j num
69 Number of jobs to perform in parallel.
70
71 --progress
72 Display progress indicators for long-lasting operations, such as
73 network transfers, building, etc.
74
75 --no-progress
76 Suppress progress indicators for long-lasting operations, such
77 as network transfers, building, etc.
78
79 --diag-color
80 Use color in diagnostics.
81
82 --no-diag-color
83 Don't use color in diagnostics.
84
85 --bpkg path
86 The package manager program to be used for build configuration
87 management.
88
89 --bpkg-option opt
90 Additional option to be passed to the package manager program.
91
92 --build path
93 The build program to be used to build packages.
94
95 --build-option opt
96 Additional option to be passed to the build program.
97
98 --curl path
99 The curl program to be used for network operations.
100
101 --curl-option opt
102 Additional option to be passed to the curl program.
103
104 --pager path
105 The pager program to be used to show long text.
106
107 --pager-option opt
108 Additional option to be passed to the pager program.
109
110 --options-file file
111 Read additional options from file.
112
113 --default-options dir
114 The directory to load additional default options files from.
115
116 --no-default-options
117 Don't load default options files.
118
120 See bdep-default-options-files(1) for an overview of the default op‐
121 tions files. For the fetch command the search start directory is the
122 project directory. The following options files are searched for in each
123 directory and, if found, loaded in the order listed:
124
125 bdep.options
126 bdep-fetch.options
127
128 The following fetch command options cannot be specified in the default
129 options files:
130
131 --directory|-d
132
134 Send bug reports to the users@build2.org mailing list.
135
137 Copyright (c) 2014-2023 the build2 authors.
138
139 Permission is granted to copy, distribute and/or modify this document
140 under the terms of the MIT License.
141
142
143
144bdep 0.16.0 June 2023 bdep-fetch(1)