Open vanzod opened 6 years ago
There's actually a way around this... You can avoid that the existing modules get removed by specifying a custom separate installation prefix; EasyBuild will only touch module files in the installation prefix it is configured with, not outside of that.
So, you could do something like:
eb --from-pr 1234 --force --robot --stop source --installpath /tmp/$USER/pr1234-${RANDOM}
That doesn't mean we shouldn't provide an easier way though :)
A better way to check checksums provided in easyconfig files should be implemented.
Currently when checking easyconfig PRs that only update checksums, a full module rebuild is required. Using
--stop source
does not provide a viable solution since the corresponding installed module is deleted before the source fetching step, which breaks Lmod module dependencies.Additionally, it would be great if EB could check the checksum of a easyconfig file even if its dependencies cannot be satisfied.