SPEC2SCL(1)

πŸ“¦ version 1.2.2, in fedora 43, fedora 44

✨ NAME ✨

spec2scl β€” the manual page for spec2scl, bestie. That's it, that's the name, we move.


πŸŽ€ DESCRIPTION πŸŽ€

okay so real talk, here's how you run this thing:

usage: spec2scl [-h] [-V] [-i] [-r] [-b] [-k SKIP_FUNCTIONS] [-n | -l SCL_CONTENTS_LIST] [--meta-specfile METAPACKAGE_NAME] [-v VARIABLES] [ARGUMENT [ARGUMENT ...]]

Convert RPM specfile to be SCL ready. That's the whole job. She takes your normie RPM specfile and gives it that SCL makeover πŸ’…

🌸 positional arguments 🌸

  • ARGUMENT β€” the path(s) to the specfile(s). Plural, babes. You can hand her more than one.

πŸ¦‹ optional arguments πŸ¦‹

  • -h, --help β€” shows this help message and dips. classic.
  • -V, --version β€” shows the spec2scl version, so you know what you're working with.
  • -i β€” convert in place, meaning she replaces the old specfiles with the new generated ones. Mandatory when multiple specfiles are to be converted, so don't skip it if you're batch-processing, or it's giving chaos.
  • -r, --no-meta-runtime-dep β€” don't add the runtime dependency on the scl runtime package. she'll simply not. πŸ™ˆ
  • -b, --no-meta-buildtime-dep β€” don't add the buildtime dependency on the scl runtime package. same energy, different dependency.
  • -k SKIP_FUNCTIONS, --skip-functions SKIP_FUNCTIONS β€” a comma separated list of transformer functions to skip. tell her which ones to leave alone.
  • -n, --no-deps-convert β€” don't convert dependency tags. Mutually exclusive with -l, so pick a lane bestie, you cannot have both.
  • -l SCL_CONTENTS_LIST, --list-file SCL_CONTENTS_LIST β€” the list of the packages/provides that will be in the SCL, so she can convert Requires/BuildRequires properly. The lines in the file are in form of "pkg-name %{?custom_prefix}", where the prefix part is optional. (yes, the quotes are in the file format. keep them, iykyk.)

πŸ‘‘ metapackage arguments πŸ‘‘

  • --meta-specfile METAPACKAGE_NAME β€” produce a metapackage specfile based on the metapackage name provided. go check the SCL docs for metapackage naming, fr fr, don't freestyle that part.
  • -v VARIABLES, --variables VARIABLES β€” list of variables separated with comma. Used only with the --meta-specfile option, so don't come at her with -v alone, it's giving nothing.

πŸ’– EXAMPLES πŸ’–

the vibes, demonstrated:

spec2scl [SPECFILE_PATH]

Convert an RPM specfile into an SCL specfile. the classic glow-up ✨

spec2scl -i [SPECFILE_PATH [SPECFILE_PATH ...]]

Convert one or more RPM specfiles into SCL specfiles and replace the original files. bold. fearless. irreversible-ish.

spec2scl --meta-specfile [METAPACKAGE_NAME]

Create a specfile for a metapackage with a name METAPACKAGE_NAME. main character metapackage behavior, honestly. πŸ‘‘


🐍 LANGUAGE 🐍

PYTHON


πŸ“œ LICENCE πŸ“œ

MIT β€” permissive queen. do what you want, just keep the notice.


🌟 AUTHOR 🌟

Writen by Slavek Kabrda, Robert Kuska, Iryna Shcherbina 🫢 absolute legends, no cap.


and that's the whole page, bestie β€” SPEC2SCL(1), living in the General Commands Manual, section 1, right where she belongs. go convert something pretty πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from