Split $releasever to $releasever_major and $releasever_minor #1989
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.
Whenever the
releasever
substitution variable is set, automatically derive and set thereleasever_major
andreleasever_minor
vars by splittingreleasever
on the first ".".Companion to the DNF 5 implementation here: rpm-software-management/dnf5#800. This implementation is kept similar to the implementation in DNF 5, including the caveat/potentially breaking change that setting a substitution variable can now raise an exception. If we don't want to raise an error, a simple solution would be simply to allow setting of
$releasever_major
and$releasever_minor
and take out theReadOnlyVariableError
.DNF 5 issue: rpm-software-management/dnf5#710
For https://bugzilla.redhat.com/show_bug.cgi?id=1789346, but merging this does not close the bug yet; the shell-style variable expansion still needs to be implemented.