Hello When I’m trying to update older easyconfigs with newer upstream releases, and for newer toolchains, what’s the best way of finding out whether patches that were in use a while ago are still relevant?
A case I’m looking at right now is numpy. I’d like to build the latest version for goolf-1.7.20. The newest easyconfig for goolf is 1.7.1, which still refers to a patch: patches = ['numpy-%(version)s_distutils_multiple-lib-dirs.patch’] while the newest intel easyconfig (1.9.2) refers to a different patch: patches = ['numpy-1.8.0-mkl.patch’] Other than checking the code manually, is there a way of tracking why these patches were applied? I see there’s a PR, as yet unmerged: https://github.com/hpcugent/easybuild-easyconfigs/pull/1178 I suppose I’m missing something like the changelog that you have in RPM .spec files, that (at least in theory) explains such changes. Cheers, Adam — Adam Huffman Senior HPC and Cloud Systems Engineer The Francis Crick Institute Gibbs Building 215 Euston Road London NW1 2BE T: 020 7611 2244 E: [email protected] W: www.crick.ac.uk The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.
