RHEL9: Add packages for dracut modules explicitly (don't rely on weak dependencies) #267
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For installers (both Anaconda and CoreOS) on RHEL 9, we define a couple of dracut modules that rely on packages that are pulled in as weak dependencies of other packages in the installer package set. Let's define these explicitly instead.
For other packages that are required by other modules, let's still rely on package "hard" dependencies that are already defined.
In the future, we should derive the required packages dynamically from the dracut modules defined in the pipeline.
I've verified this works by applying the following patch and building installers:
Applying the same patch on (current)
main
and building an installer should fail at the dracut stage.This is not an issue on RHEL 8 and Fedora. The package sets for installers include packages with hard dependencies on the modules.