We should probably tag the version of jasmin-sci in github with each new release. Currently we just use the main branch.
Probably internally we should have a build procedure that involves seperate devel and build platforms and which rebuilds everything each time using the build_all script, and which then publishes the RPMs to the repo. (So far, it has been rather more ad-hoc: rebuild and publish just the components known to have been changed, then push the updated spec files to github.) The details of how to publish for use on JASMIN as part of the production build will have to go into an appropriate non-public repo, but any changes to the build script can be here on github.
We should probably tag the version of jasmin-sci in github with each new release. Currently we just use the main branch.
Probably internally we should have a build procedure that involves seperate devel and build platforms and which rebuilds everything each time using the
build_allscript, and which then publishes the RPMs to the repo. (So far, it has been rather more ad-hoc: rebuild and publish just the components known to have been changed, then push the updated spec files to github.) The details of how to publish for use on JASMIN as part of the production build will have to go into an appropriate non-public repo, but any changes to the build script can be here on github.