aurora/build_files/dx/usr/share/dnf5/repos.d
renner 728717d75e
refactor: use dnf do for some 3rd-party repositories (#2983)
In the past we have moved away from doing big dnf transactions spanning
multiple rpm repositories [1] because of the associated risk of third
party repos injecting packages we expect to get from Fedora. With this
we explicitly set which packages are allowed to be installed from each
repo. This means we still get to do big transactions which are generally
faster.

The downside of this is that if subpackages or dependencies from a
3rd-party repo get introduced/change then our builds will break, I think
this is fine as the ones I'm changing here have been unchanging for a
while.

This should only touch repositories with a very specific purpose/single
projects.

This purposefully doesn't touch any ublue-os coprs or negativo (also
they are difficult to handle as we use them in the nvidia script [2]),
those are the only mono-repos so outright excluding the packages is not
an easy option as we would make custom image builds (and usr-overlays
for testing) more annoying.

[1] https://github.com/ublue-os/aurora/issues/1115
[2] 1e4d10b9ac/build_files/nvidia/nvidia-install.sh
2026-10-10 17:30:41 +02:00
..
_copr:copr.fedorainfracloud.org:karmab:kcli.repo refactor: use dnf do for some 3rd-party repositories (#2983) 2026-10-10 17:30:41 +02:00
docker-ce.repo refactor: use dnf do for some 3rd-party repositories (#2983) 2026-10-10 17:30:41 +02:00
vscode.repo refactor: use dnf do for some 3rd-party repositories (#2983) 2026-10-10 17:30:41 +02:00