// file : bpkg/pkg-build.cli // copyright : Copyright (c) 2014-2016 Code Synthesis Ltd // license : MIT; see accompanying LICENSE file include ; "\section=1" "\name=bpkg-pkg-build" "\summary=build package" namespace bpkg { { " ", "\h|SYNOPSIS| \c{\b{bpkg pkg-build}|\b{build} [] ([/] | | /)...} \h|DESCRIPTION| The \cb{pkg-build} command builds one or more packages including all their prerequisites. Each package can be specified as just the name () with optional package version () in which case the package will be automatically fetched from one of the repositories. See the \l{bpkg-cfg-add(1)} and \l{bpkg-cfg-fetch(1)} commands for more information on package repositories. Alternatively, the package can be specified as either the path to the package archive () or to the package directory (/; note that it must end with a directory separator). See the \l{bpkg-pkg-fetch(1)} and \l{bpkg-pkg-unpack(1)} commands for more information on the semantics of specifying the package as an archive or a directory. Packages that are specified explicitly on the command line will be \i{held}, that is, they will not be considered for automatic removal if they no longer have any dependents. Packages that are specified with the explicit package version () or as an archive or directory, will, in addition, have their versions held, that is, they will not be automatically upgraded. The \cb{pkg-build} command also supports several \cb{--*-only} options that allow you to limit the amount of work that will be done." } class pkg_build_options: configuration_options { "\h|PKG-BUILD OPTIONS|" bool --yes|-y { "Assume the answer to all prompts is \cb{yes}." } bool --keep-prerequisite { "Don't offer to drop prerequsite packages that were automatically built and will no longer be necessary." } bool --print-only|-p { "Print to \cb{STDOUT} what would be done without actually doing anything." } bool --configure-only|-c { "Configure all the packages but don't update." } }; }