aboutsummaryrefslogtreecommitdiff log msg author committer range
path: root/bpkg/pkg-build.cli
diff options
 context: 12345678910152025303540 space: includeignore mode: unifiedssdiffstat only
Diffstat (limited to 'bpkg/pkg-build.cli')
-rw-r--r--bpkg/pkg-build.cli43
1 files changed, 25 insertions, 18 deletions
 diff --git a/bpkg/pkg-build.cli b/bpkg/pkg-build.cliindex e247f47..0ac8dcb 100644--- a/bpkg/pkg-build.cli+++ b/bpkg/pkg-build.cli@@ -13,7 +13,8 @@ namespace bpkg { " - + + ",@@ -25,12 +26,13 @@ namespace bpkg \b{bpkg pkg-build}|\b{build} [] \ \b{--upgrade}|\b{-u} | \b{--patch}|\b{-p}\n \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ [... \b{--}]} - \c{ = [](([\b{:}][\b{/}])\b{,}...[\b{@}] | \n- \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ [\b{@}] \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ | \n- \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ | \n+ \c{ = [](([\b{:}][])\b{,}...[\b{@}] | \n+ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ [\b{@}] \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ | \n+ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ | \n \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \b{/})\n- \ \ \ \ = \b{?}\n- \ \ = \b{sys}}+ \ \ \ \ \ \ = \b{?}\n+ \ \ \ \ = \b{sys}\n+ \ \ \ = \b{/} | } \h|DESCRIPTION| @@ -56,21 +58,25 @@ namespace bpkg or \cb{--patch}. Each package can be specified as just the name () with optional- package version () in which case the source code for the package- will be automatically fetched from one of the configured+ version specification (), in which case the source code for the+ package will be automatically fetched from one of the configured repositories. See the \l{bpkg-rep-add(1)} and \l{bpkg-rep-fetch(1)}- commands for more information on package repositories. If is not- specified, then the latest available version will be built. To downgrade,- the desired version must be specified explicitly. For example:+ commands for more information on package repositories. The version+ specification () can be either the exact version in the+ \c{\b{/}\i{version}} form or the version constraint as described in+ \l{bpkg#package-version-constraint Package Version Constraint}. If+ is not specified, then the latest available version will be+ built. To downgrade, the desired version must be specified+ explicitly. For example: \- bpkg build foo libfoo/1.2.3+ bpkg build foo libfoo/1.2.3 \"bar < 2.0.0\" \ Alternatively, the package repository location () can be- specified as part of the build command. In this case, if is not- specified, then the latest available from this repository version will be- built. For example:+ specified as part of the build command. In this case, if is+ not specified, then the latest available from this repository version+ will be built. For example: \ bpkg build foo,libfoo/1.2.3@https://git.example.org/foo.git#master@@ -91,8 +97,9 @@ namespace bpkg (). Currently the only recognized scheme is \cb{sys} which instructs \cb{pkg-build} to configure the package as available from the system rather than building it from source. If the system package version- () is not specified or is '\cb{*}', then it is considered to be- unknown but satisfying any dependency constraint. If the version is not+ () is not specified or is '\cb{/*}', then it is considered to+ be unknown but satisfying any version constraint. If specified,+ may not be a version constraint. If the version is not explicitly specified, then at least a stub package must be available from one of the repositories. @@ -125,7 +132,7 @@ namespace bpkg available for build as a dependency. Packages (both built to hold and as dependencies) that are specified with- an explicit package version () or as an archive or directory,+ an explicit package version () or as an archive or directory, will have their versions held, that is, they will not be automatically upgraded.