Packaging: add a dependency on Slurm version for RPM packages #158
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.
Slurm SPANK plugins need to be recompiled for each major Slurm version. To make upgrades easier and avoid confusion, this PR proposes to add a dependency on the version of Slurm that's installed on the system, and add that major version in the generated RPM release info.
For instance, building RPMs for Pyxis 0.20 on a el9 host with Slurm 24.11 RPMs will create a
nvslurm-plugin-pyxis-0.20.0-1.slurm2411.el9.x86_64.rpm
package, with a dependency onlibslurm.so.42()(64bit)
.To do this, we get the version of the installed
slurm-devel
RPM package in the SPEC file, via arpm -q
command. Doing this uses the "%{VERSION}" RPM tag, which conflicts withVERSION
variable that is used in theMakefile
and passed torpmbuild
. So to avoid unwanted expansion of that%{VERSION}
variable, it's been renamed toPYXIS_VER
in the Makefile.