alpm-srcin...t-packages(1)

💖 NAME 💖

okay so welcome to the alpm-srcin...t-packages(1) page from the General Commands Manual, bestie! The main character is alpm-srcinfo-format-packages — Format a SRCINFO file's packages from a path or stdin. That's literally the whole vibe: you point it at a SRCINFO file (or pipe stuff in) and it formats the packages. ✨

✨ SYNOPSIS ✨

the shape of it is exactly this, no cap:

alpm-srcinfo format-packages [-s|--schema] <-a|--architecture>
       [-o|--output-format] [-p|--pretty] [-h|--help] [FILE]

🦋 DESCRIPTION 🦋

Read, validate and print all of the SRCINFO's packages in their final representation for a specific architecture. That's the job, and it ate. 🫶

If the file is valid, the program prints the data in the requested file format to stdout and returns with an exit status of 0. Slay. ✅

💅 OPTIONS 💅

• -s, --schema <VERSION> — Provide the SRCINFO schema version to use.
  • If no schema version is provided, it will be deduced from the file itself.
• -a, --architecture <ARCHITECTURE> — The selected architecture that should be used to interpret the SRCINFO file.
  • Only [split-]packages that are applicable for this architecture will be returned.
• -o, --output-format <OUTPUT_FORMAT> [default: json] — Provide the output format.
  • Possible values:
    • json: The JSON output format
• -p, --pretty — Pretty-print the output.
  • Only applies to formats that support pretty output and is otherwise ignored.
• -h, --help — Print help (see a summary with '-h').
• [FILE] — An optional input file path to read from.
  • If no file is specified, stdin is read from and expected to contain PKGINFO data to validate.

and that's the page, bestie! 🎀 footer source/version vibes: alpm-srcinfo-format-packages and alpm-srcin...t-packages(1). date: not actually listed in that footer line, so i'm not inventing one — periodt. 💅