bpkg-pkg-configure(1)

📦
version 0.17.0 · 2 versions
, in fedora 43, fedora 44, nixos 26.05

💖 bpkg-pkg-configure — configure package 💖

okay bestie, welcome to the bpkg-pkg-configure(1) page, part of the bpkg manual ✨ this is the glow-up era of your packages, fr fr.

🌸 NAME 🌸

bpkg-pkg-configure — configure package 👑

🎀 SYNOPSIS 🎀

bpkg pkg-configure [options] [cfg-var...] pkg

🦋 DESCRIPTION 🦋

so pkg-configure is the one that configures stuff. and it configures either:

  • the source code package you already unpacked (that's bpkg-pkg-unpack(1), bpkg-pkg-checkout(1) — you know, the whole unpack-and-checkout pipeline 💅), or
  • a package that's already present in the system.

A source code package inherits all the common build2 configuration values you specified back when you created the configuration (bpkg-cfg-create(1)). and then — plot twist — you can pass it extra package-specific configuration variables through pkg-configure (cfg-var). it's giving customization. it's giving ✨personalized✨.

A system package gets specified with the sys:pkg[/ver] syntax. no cap. and here's the tea: if you don't give the package version (ver), it's considered unknown but still satisfying any dependency constraint. and that lil mystery version? displayed as *. iconic honestly ⭐

💅 PKG-CONFIGURE OPTIONS 💅

  • --directory|-d dir — pretend the configuration lives in dir instead of whatever the current working directory is. like a lil address change 🏠

🌈 COMMON OPTIONS 🌈

okay so these are the common options, summarised here with the full detailed version living over in bpkg-common-options(1). go read that for the director's cut 🎬

  • -v — print the essential underlying commands as they get executed. the highlight reel 🎥
  • -V — print all the underlying commands being executed. the full unedited footage 😭
  • --quiet|-q — run quietly, only printing error messages. shhh mode 🤫
  • --verbose level — set the diagnostics verbosity to level, somewhere between 0 and 6. pick your vibe check 📶
  • --stdout-format format — the representation format used for printing to stdout. dress code for your output 💅
  • --jobs|-j num — how many jobs to do in parallel. multitasking queen energy 👑
  • --no-result — don't print the informational messages about the outcome of running a command or some of its parts. no commentary, just vibes 🙈
  • --structured-result fmt — write the result of running a command in a structured form. organized bestie 🗂️
  • --progress — display progress indicators for long-lasting operations, like network transfers, building, etc. we love a loading bar 🍓
  • --no-progress — suppress those progress indicators for long-lasting operations, like network transfers, building, etc. ✋
  • --diag-color — use color in diagnostics. pretty errors 🌸
  • --no-diag-color — don't use color in diagnostics. minimalism era 🤍
  • --build path — the build program used to build packages. your builder fr 🔨
  • --build-option opt — an additional option to pass to the build program. extra lil note 💌
  • --fetch path — the fetch program used to download resources. go get it 🏃
  • --fetch-option opt — an additional option to pass to the fetch program.
  • --fetch-timeout sec — the timeout for the fetch and fetch-like programs (for example, git). ⏰
  • --pkg-proxy url — the HTTP proxy server to use when fetching package manifests and archives from remote pkg repositories. middleman moment 🫶
  • --git path — the git program used to fetch git repositories.
  • --git-option opt — an additional common option to pass to the git program.
  • --sha256 path — the sha256 program used to calculate SHA256 sums. math but make it secure 🔐
  • --sha256-option opt — an additional option to pass to the sha256 program.
  • --tar path — the tar program used to extract package archives. unzip era 📦
  • --tar-option opt — an additional option to pass to the tar program.
  • --openssl path — the openssl program used for crypto operations. 🔒
  • --openssl-option opt — an additional option to pass to the openssl program.
  • --auth type — types of repositories to authenticate. who goes there 🕵️
  • --trust fingerprint — trust a repository certificate with a SHA256 fingerprint. i trust you bestie 🤝
  • --trust-yes — assume the answer to all authentication prompts is yes. ✅
  • --trust-no — assume the answer to all authentication prompts is no. ❌
  • --git-capabilities up=pc — protocol capabilities (pc) for a git repository URL prefix (up). leveling up your git game ⬆️
  • --pager path — the pager program used to show long text. for the long reads 📖
  • --pager-option opt — an additional option to pass to the pager program.
  • --options-file file — read additional options from file. extra homework 📝
  • --default-options dir — the directory to load additional default options files from. 🗃️
  • --no-default-options — don't load default options files. skip the defaults, we're going rogue 🙅
  • --keep-tmp — don't remove bpkg's temporary directory at the end of the command execution, and print its path at verbosity level 2 or higher. keep the receipts 🧾

✨ DEFAULT OPTIONS FILES ✨

want the overview of default options files? it's all in bpkg-default-options-files(1), go check it 🫶

for the pkg-configure command specifically, the search start directory is the configuration directory.

these options files get searched for in each directory, and if they're found, they're loaded in the order listed:

bpkg.options
bpkg-pkg-configure.options
🚨 and listen — these pkg-configure command options cannot be specified in the default options files: - --directory|-d

💀 BUGS 💀

found a bug? send those bug reports to the users@build2.org mailing list. we take those fr fr 📬

Copyright (c) 2014-2024 the build2 authors.

Permission is granted to copy, distribute and/or modify this document under the terms of the MIT License. slay, legally speaking 💜

and that's the whole page, bestie!! 🎀 this lil rewrite rode in on bpkg 0.17.0, dated June 2024, and it's the bpkg-pkg-configure(1) manual through and through. mwah 💋 go configure something iconic 🦋✨

📦 where this page comes from