wunker-os/modules/dnf

dnf

The dnf module offers pseudo-declarative package and repository management using dnf.

The module first downloads the repository files from URLs declared under repos: into /etc/yum.repos.d/. The magic string %OS_VERSION% can be substituted with the current VERSION_ID (major Fedora version), which can be used, for example, for pulling correct versions of repositories which have fixed Fedora version in the URL.

You can also add repository files directly into your git repository if URLs are not provided. For example:

repos:
   - my-repository.repo # copies in .repo file from files/dnf/my-repository.repo to /etc/yum.repos.d/

Specific COPR repositories can also be specified in COPR user/project format & is prefered over using direct COPR URL.

If you use a repo that requires adding custom keys (eg. Brave Browser), you can import the keys by declaring the key URLs under keys:. The magic string acts the same as it does in repos.

Then the module installs the packages declared under install: using dnf -y install --refresh, it removes the packages declared under remove: using dnf -y remove. If there are packages declared under both install: and remove: then removal is performed 1st & install 2nd.

Installing RPM packages directly from a http(s) url that points to the RPM file is also supported, you can just put the URLs under install: and they'll be installed along with the other packages. The magic string %OS_VERSION% is substituted with the current VERSION_ID (major Fedora version) like with the repos: property.

If an RPM is not available in a repository or as an URL, you can also install it directly from a file in your git repository. For example:

install:
   - weird-package.rpm # tries to install files/dnf/weird-package.rpm

Additionally, the dnf module supports a fix for packages that install into /opt/. Installation for packages that install into folder names declared under optfix: are fixed using some symlinks. Directory path in /opt/ for those packages should be provided in recipe, like in Example Configuration.

There is an option to install & remove RPM groups if desired in group-install: & group-remove:. RPM groups removal & installation always run before packages removal & installation. To see the list of all available RPM groups, you can use dnf group list command.

The module can also replace base RPM packages with packages from any repo. Under replace:, the module finds every pair of keys - from-repo: and packages:. (Multiple pairs are supported.) The module uses - from-repo: key to gather the repo for package replacement, then it replaces packages declared under packages: using the command dnf -y distro-sync --refresh --repo "${repo}" "${packages}". The magic string %OS_VERSION% is substituted with the current VERSION_ID (major Fedora version) as already said above. You need to assure that you provided the repo in repos: before using replacement functionality. To gather the repo ID that you need to input, you can use dnf repo list command.

:::note Removed packages are still present in the underlying ostree repository, what remove does is kind of like hiding them from the system, it doesn't free up storage space. :::

dnf behavior options

There are several options that can be enabled during the package/group install + removal & during package replace, which modify the behavior of the package manager during those operations.

Those include:

Install operation:

• install-weak-dependencies (--setopt=install_weak_deps=True/False flag)
• skip-unavailable-packages (--skip-unavailable flag)
• skip-broken-packages (--skip-broken flag)
• allow-erasing-packages (--allowerasing flag)

Remove operation:

• remove-unused-dependencies (--no-autoremove flag)

dnf install/replace behavior options

install-weak-dependencies

install-weak-dependencies option is used to enable or disable installation of weak dependencies for every install & replace operation. By default, this option is true, which means that weak dependencies are installed by default. Which kind of dependencies are considered weak can be seen here.

skip-unavailable-packages

skip-unavailable-packages option is used to continue or abort install/replace operation if there are no packages available in the repo in install operation, or if they are not available in the system in replace operation. By default, this option is false, which means that install/replace operation aborts in case of unavailable packages.

skip-broken-packages

skip-broken-packages option is used to continue or abort install/replace operation if there are broken packages in the system. By default, this option is false, which means that install/replace operation aborts in case of broken packages.

allow-erasing-packages

allow-erasing-packages option is used to allow erasing/removing problematic packages if they cause issues in install/replace operation. By default, this option is false, which means that problematic packages won't be removed & operation will be aborted.

dnf package (non-group) removal behavior options

remove-unused-dependencies

remove-unused-dependencies option is used to control the behavior of removing unused dependencies when some main packages are removed. By default, this option is true. Only compatible with removing packages, not compatible with removing RPM groups.