compose-write-repo-file(1)

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

πŸ’– compose-write-repo-file β€” a whole manual, but make it cute πŸ’–

okay bestie, so this is a page from the General Commands Manual, and it's all about compose-write-repo-file. no cap, it's lowkey one of those little utilities that just does the thing, and we're gonna go through every single crumb of it together. grab a snack πŸ“


✨ NAME ✨

compose-write-repo-file β€” write a .repo file pointing to a compose πŸŽ€

that's it. that's the name. iconic.


🌸 SYNOPSIS 🌸

compose-write-repo-file [OPTIONS...]  COMPOSE_PATH

yeah, that's the whole vibe: some options, then a COMPOSE_PATH, and you're off. (yes there are two spaces there, we do not question the formatting gods 🫢)


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea: compose-write-repo-file loads metadata from a compose and then creates a YUM/DNF configuration file with entries for the repositories in that compose.

literally that's the whole job. it looks at your compose, goes "mm yes repos", and hands you back a config file. main character energy tbh. πŸ’…


πŸ‘‘ OPTIONS πŸ‘‘

every flag, every crumb, no skipping, periodt:

  • -h, --help β€” print help and exit. the classic. the legend. 🫢
  • --arch=ARCH β€” use URLs with this hardcoded architecture. by default, $basearch is used instead. (iykyk, sometimes you just wanna be specific ✨)
  • --include-debuginfo β€” create entries for debuginfo repositories. more repos, more love πŸ›
  • --include-source β€” create entries for source repositories. πŸ“¦
  • --variant=VARIANT β€” create entries only for the listed variants. you can use this one multiple times, go off. any variants that don't include repositories are skipped automatically, so no awkward empty entries πŸ’€
  • --disabled=VARIANT β€” make the entries for this variant disabled. by default, all repositories are created as enabled. so this is the "actually, sit this one out" button πŸ™ˆ
  • --output=FILE_PATH β€” write the output to this file instead of to stdout. very demure, very file-based πŸŽ€
  • --translate=PATH_PREFIX,URL_PREFIX β€” by default, local filepaths are created. with this option it's possible to generate URLs. the path prefix gets stripped from the path, and replaced with the URL prefix. glow-up for your paths ✨
  • --name-pattern=PATTERN β€” customize the name for the repositories. these fragments are available:
    • release_id, release_short, release_name, release_version, release_type, release_major_version
    • base_product_short, base_product_name, base_product_version, base_product_type (these are only available for layered product composes)
    • compose_id, compose_type, compose_date, compose_respin, label
    • variant (should always be used unless a single variant is processed)
    • arch (only makes sense if --arch is used)

the default is:

{release_short}-{release_version}-{variant}

so yeah, mix and match those fragments and name your repos whatever your heart desires πŸ’–

  • --gpgcheck β€” enable gpgcheck = 1. default is gpgcheck = 0. πŸ”
  • --gpgkey=GPGKEY β€” the gpgkey value (public key URL). multiple key URLs should be comma-separated. use --gpgcheck with this option. πŸ”‘ (they're a package deal, fr fr)

πŸ”₯ EXIT CODE πŸ”₯

the exit code is always 0 on success, and non-zero if there was a problem loading the compose.

so like, 0 = slay, non-zero = something went sideways while loading the compose 😭


πŸ’€ BUGS πŸ’€

found a bug? bestie, please report it at:

https://pagure.io/compose-utils/issues

they wanna hear about it, no gatekeeping 🫢


lowkey a reminder that this is a manpage for compose-write-repo-file in the General Commands Manual β€” if you ever need the official version, it's right there waiting for you πŸ’œ

and that's the whole page, bestie β€” written by the compose-utils girlies, dated like all good manpages are, and signed off with love. compose-write-repo-file(1) forever πŸ‘‘βœ¨πŸŽ€

πŸ“¦ where this page comes from