Skip to content

carapace-sh/carapace-bin / skills/dnf5

Use when working with dnf5 — the next-generation RPM package manager for Fedora/RHEL. Covers CLI commands and options, configuration, plugin system (dnf5 active plugins and libdnf5 passive plugins), dnf5daemon D-Bus API, execution workflow, package specs (NEVRA), modularity, caching, migration from DNF4, libdnf5 library architecture, build system, and command-line aliases. Triggers on: "dnf5", "dnf", "libdnf5", "libdnf", "dnf5daemon", "dnf5-plugins", "libdnf5-plugins", "dnf5.conf", "repoquery", "versionlock", "distro-sync", "offline upgrade", "system-upgrade", "advisory", "comps", "modulemd", "NEVRA", "installroot", "forcearch", "repo variables", "metadata_expire", "setopt", "setvar", "config-manager", "repofrompath", "releasever", "basearch", "pluginpath".

FileKindSize
SKILL.mdskill md9.1 KB
references/aliases.mdmarkdown4.6 KB
references/build.mdmarkdown6.1 KB
references/caching.mdmarkdown4.6 KB
references/cli.mdmarkdown8.1 KB
references/comps.mdmarkdown1.7 KB
references/configuration.mdmarkdown15.7 KB
references/daemon.mdmarkdown13.4 KB
references/filtering.mdmarkdown2.2 KB
references/forcearch.mdmarkdown1.5 KB
references/installroot.mdmarkdown2.5 KB
references/libdnf5.mdmarkdown7.0 KB
references/migration.mdmarkdown8.5 KB
references/modularity.mdmarkdown4.1 KB
references/plugins.mdmarkdown16.2 KB
references/repo-variables.mdmarkdown2.4 KB
references/specs.mdmarkdown4.2 KB
references/system-state.mdmarkdown2.0 KB
references/workflow.mdmarkdown7.5 KB

references/repo-variables.md

View on GitHub
# DNF5 Repo Variables

Repository variables available for substitution in DNF5 repository configuration files.

> **Source of truth**: <https://dnf5.readthedocs.io/en/stable/dnf5.conf.5.html>.

## Built-in Variables

| Variable | Description | Overridable? |
|----------|-------------|--------------|
| `$arch` | System's CPU architecture (e.g., `aarch64`, `i586`, `i686`, `x86_64`) | No — cannot be overridden by variable files or env vars |
| `$basearch` | Base architecture. e.g., `i686`/`i586` -> `i386`; AMD64/Intel64 -> `x86_64` | No — cannot be overridden by variable files or env vars |
| `$releasever` | Release version of the OS, derived from RPMDB | Yes — via `--releasever` CLI option or `--setvar=releasever=VALUE` |
| `$releasever_major` | Major part of releasever (before first `.`) | Yes — via `--releasever-major` or auto-set from `--releasever` |
| `$releasever_minor` | Minor part of releasever (after first `.`) | Yes — via `--releasever-minor` or auto-set from `--releasever` |

## User-Defined Variables

### Via Variable Files

Place files in `/etc/dnf/vars/` (or `/usr/share/dnf5/vars.d/` for distribution). The filename is the variable name (lowercase, alphanumeric + underscores). The file content is the variable value.

```
# /etc/dnf//my_variable
my_value
```

Used as `$my_variable` in config files.

### Via Environment Variables

Set environment variables prefixed with `DNF_VAR_`:

```bash
export DNF_VAR_MY_VARIABLE=value
```

Used as `$MY_VARIABLE` in config files (without the prefix).

Variable name can only contain alphanumeric characters and underscores.

### Legacy Numbered Variables

`DNF0` through `DNF9` environment variables:

```bash
export DNF1=value
```

Used as `$DNF1` in config files.

### YUM Compatibility

Variables are also read from `/etc/yum/vars/` for YUM compatibility.

## Substitution

Variable substitution is performed on:
- Repository ID
- All repository configuration values (`baseurl`, `metalink`, `mirrorlist`, `gpgkey`, etc.)
- Repo paths from `--repofrompath`

## Configuration

| Option | Default | Description |
|--------|---------|-------------|
| `varsdir` | `/etc/dnf/vars` | Directories where variable definition files are looked for |

## Related

- [forcearch.md](forcearch.md) — `--forcearch` sets `arch` and `basearch` variables
- [installroot.md](installroot.md) — Variable resolution in installroot context
- [configuration.md](configuration.md) — `varsdir` option
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall