bpkg-cfg-info(1)

πŸ“¦
version 0.17.0 Β· 2 versions
, in fedora 43, fedora 44, nixos 26.05

πŸ’… bpkg-cfg-info(1) β€” bestie edition ✨

okay so you found the bpkg-cfg-info manual page, and honestly? it's giving "tiny command, big main character energy." let me walk you through it, no cap. 🫢


🌸 NAME 🌸

bpkg-cfg-info β€” print configuration information πŸ’–


✨ SYNOPSIS ✨

bpkg cfg-info [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the vibe: the cfg-info command prints your current configuration's absolute path, id, type, and name. that's the core four, bestie. πŸŽ€

now if you also throw in the --link and/or --backlink options, then it prints that same info for each linked and/or implicitly backlinked configuration too β€” if any exist. and listen, the dangling implicit backlinks? they get silently skipped, like they're not even in the group chat. πŸ‘» unless you specify --dangling, in which case yes bestie, we print their info too.

and ngl, super important detail: all of this info goes to stdout, not stderr. periodt. πŸ’…

if you specify --recursive together with --link and/or --backlink, then it prints this info for linked and/or implicitly backlinked configurations, recursively. it just keeps going. iconic behavior honestly. πŸ”₯

the output format is regular β€” each value printed on its own separate line, prefixed with the value name. and if --link, --backlink, and/or --dangling are specified, then the information blocks corresponding to linked configurations are separated with blank lines. here's an example so you can see the layout exactly:

path: /path/to/cfg/
uuid: 8d439f03-7342-4502-8b1c-74b173869478
type: target
name: foo

path: /path/to/host-cfg/
uuid: 7ee4dab3-07d9-4163-81c0-3779166a7213
type: host
name: tools

path: /path/to/build2-cfg/
uuid: d453aa2a-92c4-4066-87e4-c8672eed06e1
type: build2
name: modules

see? cute little blocks. 🌈


🌟 CFG-INFO OPTIONS 🌟

  • --link β€” Print linked configurations. πŸ”—
  • --backlink β€” Print implicitly backlinked configurations. πŸ”™
  • --dangling β€” Print dangling implicit backlinks. πŸ‘»
  • --recursive β€” Print linked configurations recursively. πŸŒ€
  • --directory|-d dir β€” Assume configuration is in dir rather than in the current working directory. πŸ“

πŸŽ€ COMMON OPTIONS πŸŽ€

these are the common options, summarized below β€” and if you want the full detailed description, it's over in bpkg-common-options(1). iykyk. ✨

  • -v β€” Print essential underlying commands being executed. πŸ”
  • -V β€” Print all underlying commands being executed. πŸ”πŸ”
  • --quiet|-q β€” Run quietly, only printing error messages. 🀫
  • --verbose level β€” Set the diagnostics verbosity to level between 0 and 6. πŸ“Ά
  • --stdout-format format β€” Representation format to use for printing to stdout. πŸ–¨οΈ
  • --jobs|-j num β€” Number of jobs to perform in parallel. ⚑
  • --no-result β€” Don't print informational messages about the outcome of performing a command or some of its parts. πŸ™ˆ
  • --structured-result fmt β€” Write the result of performing a command in a structured form. πŸ“‹
  • --progress β€” Display progress indicators for long-lasting operations, such as network transfers, building, etc. πŸ“Š
  • --no-progress β€” Suppress progress indicators for long-lasting operations, such as network transfers, building, etc. πŸš«πŸ“Š
  • --diag-color β€” Use color in diagnostics. 🌈
  • --no-diag-color β€” Don't use color in diagnostics. ⚫
  • --build path β€” The build program to be used to build packages. πŸ”¨
  • --build-option opt β€” Additional option to be passed to the build program. πŸ”¨βž•
  • --fetch path β€” The fetch program to be used to download resources. πŸ“₯
  • --fetch-option opt β€” Additional option to be passed to the fetch program. πŸ“₯βž•
  • --fetch-timeout sec β€” The fetch and fetch-like (for example, git) program timeout. ⏱️
  • --pkg-proxy url β€” HTTP proxy server to use when fetching package manifests and archives from remote pkg repositories. 🌐
  • --git path β€” The git program to be used to fetch git repositories. πŸ™
  • --git-option opt β€” Additional common option to be passed to the git program. πŸ™βž•
  • --sha256 path β€” The sha256 program to be used to calculate SHA256 sums. πŸ”
  • --sha256-option opt β€” Additional option to be passed to the sha256 program. πŸ”βž•
  • --tar path β€” The tar program to be used to extract package archives. πŸ“¦
  • --tar-option opt β€” Additional option to be passed to the tar program. πŸ“¦βž•
  • --openssl path β€” The openssl program to be used for crypto operations. πŸ”’
  • --openssl-option opt β€” Additional option to be passed to the openssl program. πŸ”’βž•
  • --auth type β€” Types of repositories to authenticate. πŸͺͺ
  • --trust fingerprint β€” Trust repository certificate with a SHA256 fingerprint. 🀝
  • --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). πŸ™πŸ”§
  • --pager path β€” The pager program to be used to show long text. πŸ“œ
  • --pager-option opt β€” Additional option to be passed to the pager program. πŸ“œβž•
  • --options-file file β€” Read additional options from file. πŸ“„
  • --default-options dir β€” The directory to load additional default options files from. πŸ“‚
  • --no-default-options β€” Don't load default options files. πŸš«πŸ“‚
  • --keep-tmp β€” Don't remove the bpkg's temporary directory at the end of the command execution and print its path at the verbosity level 2 or higher. πŸ—‚οΈ

🧚 DEFAULT OPTIONS FILES 🧚

okay so for the full overview of the default options files, go peek at bpkg-default-options-files(1). πŸ’œ

for the cfg-info command specifically, the search start directory is the configuration directory. and the following options files get searched for in each directory and, if found, loaded in the order listed:

bpkg.options
bpkg-cfg-info.options

and listen β€” these cfg-info command options cannot be specified in the default options files:

  • --directory|-d 🚫
like, sorry bestie, that one's not allowed in there. rules are rules. πŸ’…

πŸ’€ BUGS πŸ’€

Send bug reports to the users@build2.org mailing list. πŸ“§ (yes, actually email them, don't just vague-post about it 😭)


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. πŸ“œβœ¨


and that's the whole page, bestie!! πŸŽ€ you understood it, you slayed it, you're basically a configuration whisperer now. this was bpkg version 0.17.0, from June 2024 β€” and yes, it really is bpkg-cfg-info(1), manual page and all. mwah. πŸ’–

πŸ“¦ where this page comes from