bpkg-rep-create(1)

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

💖 bpkg-rep-create 💖

bestie. sit down. hydrate. we're talking about bpkg-rep-create — the bpkg subcommand whose whole personality is create repository. no cap, that's literally the job description. 🎀

✨ NAME ✨

bpkg-rep-create — create repository. that's it. that's the name. iconic behaviour honestly. 👑

🦋 SYNOPSIS 🦋

bpkg rep-create [options] [dir]

🌸 DESCRIPTION 🌸

okay so here's the tea ☕ — the rep-create command regenerates the packages.manifest file, and it builds it from the files that are actually present in the repository directory. it's giving "i looked at what's in the folder and i wrote it down." main character energy.

and listen 👀 — if the repositories.manifest file contains a certificate, then the signature.manifest file gets regenerated as well. in that case you must use the --key option to specify the certificate's private key. no key, no signature, we don't make the rules. 🔐

if dir is not specified, then the current working directory is used as the repository root. so if you're already standing in the right place, you can just vibe and run it. 💅

🌈 REP-CREATE OPTIONS 🌈

  • --ignore-unknown — ignore unknown manifest entries. heads up though bestie: this option also ignores the version constraints in the special toolchain build-time dependencies. so it's not just ignoring randos, it's ignoring the special ones too. 🙈
  • --min-bpkg-version _ver_ — applies backward compatibility workarounds to the generated packages.manifest file so that it can be consumed by bpkg versions greater or equal to the specified version. if unspecified, then the min-bpkg-version value from the repositories.manifest file is used, if present. and if the manifest value is not specified either, then no backward compatibility workarounds are applied. three-tier fallback, she's thorough. 💅
  • --key _name_ — private key to use to sign the repository. in most cases name will be a path to the key file, but it can also be a key id when a custom openssl cryptographic engine is used. versatile queen. 🔑

⭐ COMMON OPTIONS ⭐

the common options are summarized below, with a more detailed description available in bpkg-common-options(1). go read that one too, she ate. 🫶

  • -v — print essential underlying commands being executed.
  • -V — print all underlying commands being executed. yes, all of them. the whole group chat. 😭
  • -q, --quiet — 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.
  • -j, --jobs _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 🧚

see bpkg-default-options-files(1) for an overview of the default options files. for the rep-create command the search start directory is the repository directory.

the following options files are searched for in each directory and, if found, loaded in the order listed:

bpkg.options
bpkg-rep-create.options

and the following rep-create command options cannot be specified in the remote default options files:

  • --key
🚨 bestie this one matters: --key is banned from remote default options files. keep your private keys close, fr fr. 🔐

💀 BUGS 💀

send bug reports to the users@build2.org mailing list. they're nice, i promise. 🫶

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, no notes. this one's from bpkg 0.17.0, dated June 2024, and it's the bpkg-rep-create(1) manual page — go regenerate some repositories, you absolute legend. ✨💅🎀 slay, stay hydrated, and remember: packages.manifest isn't gonna regenerate itself. 🦋

📦 where this page comes from