BUILDINFO(5)

πŸ’– BUILDINFO β€” the makepkg build tea πŸ’–

okay bestie, so this is BUILDINFO(5) from the Pacman Manual, and it's literally the receipts for how your package got built. no cap. 🫢


✨ NAME ✨

BUILDINFO β€” Makepkg package build information file 🌸


✨ SYNOPSIS ✨

This manual page describes the format of a BUILDINFO file found in the root of a package created by makepkg. The file contains a description of the package's build environment. The information is formatted in key-value pairs separated by a =, one value per line. Arrays are represented as multiple key-value pairs having the same key.

fr fr that's the whole vibe β€” one key, one =, one value per line. arrays just keep repeating the same key like "and another one πŸ’…".

✨ DESCRIPTION ✨

This is a description of the contents of version 2 of the BUILDINFO file format. πŸ‘‘

  • format β€” Denotes the file format version, represented by a plain positive integer. it's giving "hello, I am version 2" ✨
  • pkgname β€” The name of the package. πŸŽ€
  • pkgbase β€” The base name of a package, usually the same as the pkgname except for split packages. (split packages really said "we're different πŸ’…")
  • pkgver β€” The version of the package including pkgrel and epoch.
  • pkgarch β€” The architecture of the package.
  • pkgbuild_sha256sum β€” The sha256sum in hex format of the PKGBUILD used to build the package.
  • packager β€” The details of the packager that built the package. that's you, bestie 🫢
  • builddate β€” The build date of the package in epoch.
  • builddir β€” The directory where the package was built.
  • startdir β€” The directory from which makepkg was executed.
  • buildtool β€” The name of the tool ecosystem used to set up the build environment. Used for defining a spec for reproducible builds, e.g. the source of the makepkg.conf(5) used. πŸ”₯
  • buildtoolver β€” The full version of the buildtool, for example: "$pkgver-$pkgrel-$pkgarch".
  • buildenv (array) β€” The build environment specified in makepkg.conf.
  • options (array) β€” The options set specified when building the package.
  • installed (array) β€” The installed packages at build time including the version information of the package. Formatted as "$pkgname-$pkgver-$pkgrel-$pkgarch".
not me lowkey obsessing over how installed just keeps going and going like a group chat at 2am 😭 every single package, with its version, right there.

✨ SEE ALSO ✨

makepkg(8), pacman(8), makepkg.conf(5)

See the pacman website at https://archlinux.org/pacman/ for current information on pacman and its related tools. 🌈


✨ BUGS ✨

Bugs? You must be kidding; there are no bugs in this software. But if we happen to be wrong, please report them to the issue tracker at https://gitlab.archlinux.org/pacman/pacman/-/issues with specific information such as your command-line, the nature of the bug, and even the package database if it helps.

the confidence?? iconic. but yeah, if it is bugging, spill the tea with your command-line, what the bug did, and honestly the package database too if it helps πŸ’€

✨ AUTHORS ✨

Current maintainers: πŸ’œ

  • Allan McRae <allan@archlinux.org>
  • Andrew Gregory <andrew.gregory.8@gmail.com>
  • Morgan Adamiec <morganamilo@archlinux.org>

Past major contributors: 🌟

  • Judd Vinet <jvinet@zeroflux.org>
  • Aurelien Foret <aurelien@archlinux.org>
  • Aaron Griffin <aaron@archlinux.org>
  • Dan McGee <dan@archlinux.org>
  • Xavier Chantry <shiningxc@gmail.com>
  • Nagy Gabor <ngaba@bibl.u-szeged.hu>
  • Dave Reisner <dreisner@archlinux.org>
  • Eli Schwartz <eschwartz@archlinux.org>

For additional contributors, use git shortlog -s on the pacman.git repository. 🧚


okay that's the whole page, bestie β€” go read your BUILDINFO files with main character energy πŸ‘‘βœ¨

Pacman 7.1.0 🌸 2026-10-15 β€” mwah, catch you in the next manpage πŸ’…πŸ’–

πŸ“¦ where this page comes from