EPEL has 2.1.2 which is very old. Even the current version 2.1.7 is from March 2016 so maybe this will be the last version.
I have already verified that the source RPM from EPEL for ncview can be used to build 2.1.7 just by changing the source to point to the new version ftp://cirrus.ucsd.edu/pub/ncview/ncview-2.1.7.tar.gz and bumping the version number.
Need to make it part of the SCL to avoid any possible conflicts with later versions inside EPEL.
Note - we should probably not withdraw the ncview from EPEL - then we will have both ncview and jasmin-sci-ncview (activating the SCL will prepend to PATH so that /opt/rh/jasmin-sci/root/usr/bin/ncview will be chosen over /usr/bin/ncview). This will avoid breakage for users currently using the one from EPEL without loading any module.
Want ncview 2.1.7.
EPEL has 2.1.2 which is very old. Even the current version 2.1.7 is from March 2016 so maybe this will be the last version.
I have already verified that the source RPM from EPEL for ncview can be used to build 2.1.7 just by changing the source to point to the new version
ftp://cirrus.ucsd.edu/pub/ncview/ncview-2.1.7.tar.gz
and bumping the version number.Need to make it part of the SCL to avoid any possible conflicts with later versions inside EPEL.
Note - we should probably not withdraw the ncview from EPEL - then we will have both
ncview
andjasmin-sci-ncview
(activating the SCL will prepend toPATH
so that/opt/rh/jasmin-sci/root/usr/bin/ncview
will be chosen over/usr/bin/ncview
). This will avoid breakage for users currently using the one from EPEL without loading any module.(See also helpscout ticket 41411)