RPMDEV-SPECTOOL(1)

πŸ“¦
version 9.6 Β· 4 versions
, in centos-stream 10

πŸ’… NAME πŸ’…

rpmdev-spectool β€” manual page for rpmdev-spectool 1.1.0.

okay bestie, welcome to the rpmdev-spectool(1) page β€” it's a User Commands situation, and we're gonna get into it πŸ’–.

🌸 DESCRIPTION 🌸

okay so rpmdev-spectool is literally a tool to expand and download sources and patches from specfiles ✨.

here's the usage, exactly as it comes:

usage: rpmdev-spectool [-h] [--list-files] [--get-files] [--version]
       [--all] [--sources] [--patches] [--source SOURCE] [--patch PATCH]
       [--define DEFINE] [--directory DIRECTORY] [--sourcedir] [--dry-run]
       [--force] [--debug] specfile

if you experience problems with specific specfiles, try running this on the file that's acting up:

rpmbuild --nobuild --nodeps <specfile>

it might give a clue why spectool fails on a file β€” and bestie, ignore anything about missing sources or patches when you read that output, mmkay? the plan is to catch errors like this in spectool itself and warn the user about it in the future 🫢.

πŸ₯Ί positional arguments: πŸ₯Ί

  • specfile β€” the specfile argument, the main character of this whole operation πŸ’….

✨ options: ✨

  • -h, --help β€” shows this help message and exits, no cap.

πŸŽ€ Operating mode: πŸŽ€

  • --list-files, --lf, -l β€” lists the expanded sources/patches (this is the default, bestie).
  • --get-files, --gf, -g β€” gets the sources/patches that are listed with a URL πŸ”₯.
  • --version, -V β€” prints the version and exits.

πŸ¦‹ Files on which to operate: πŸ¦‹

  • --all, -a β€” all files, sources and patches (default).
  • --sources, -S β€” all sources.
  • --patches, -P β€” all patches.
  • --source SOURCE, -s SOURCE β€” specified sources.
  • --patch PATCH, -p PATCH β€” specified patches.

🌈 Miscellaneous: 🌈

  • --define DEFINE, -d DEFINE β€” defines RPM macro 'macro' to be 'value'.
  • --directory DIRECTORY, -C DIRECTORY β€” downloads into the specified directory (default '.').
  • --sourcedir, -R β€” downloads into rpm's %{_sourcedir}.
  • --dry-run, --dryrun, -n β€” doesn't download anything, just shows what would be done.
  • --force, -f β€” tries to unlink and download if target files exist.
  • --debug, -D β€” outputs debug info, doesn't clean up when done.

okay that's the whole page, bestie 🫢 β€” brought to you by rpmdev-spectool 1.1.0, October 2024. periodt πŸ’…

πŸ“¦ where this page comes from