Initial implementation of %jp_binding macro #140
Merged
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.
Add new experimental
%jp_bindingmacro for generating binding packages, which are typically used to configure Java applications such as Maven to run with particular JVM implementation, but the mechanism is generic and can be used for other things as well.Unlike earlier implementations of binding packages, the new approach does not lead to creating conflicting packages. Instead a hierarchy of symlinks is maintained, similarly to the alternatives system.
Currently there is no way to specify which binding will be selected in case when there is more than one installed (there is nothing like priorities yet), but this subject to change in the future.
The implementation of
%jp_bindingrelies on "dynamic spec generation" (aka "specparts") feature of RPM 4.19, but later it could be updated to work with older RPM versions too. More info in RPM docs: https://rpm-software-management.github.io/rpm/manual/dynamic_specs.htmlExample usage: