Hi, I’d like to understand the policy behind the “test_dep_versions_per_toolchain_generation” test. I am maintaining the easyconfig files for TRIQS library and applications. Library and each application is a separate easyconfig. Furthermore, the update cycle of applications and libraries is not fully in sync, thus an updated application has the most recent library version as a dependency. Due to a complex dependency situation in the legacy version of the code (Python 2, but modern C++), we would like to keep using the specific version of the toolchain (foss/2019a) for this major version even for updates. What is the best way to handle this situation? Should the TRIQS library version be part of the version suffix? As in:
easyblock = 'CMakeMake' name = 'TRIQS-cthyb' version = '2.2.1' versionsuffix = '-TRIQS-2.2.3-Python-%(pyver)s’ This fails the mentioned test, however, cf. https://github.com/easybuilders/easybuild-easyconfigs/pull/11101 <https://github.com/easybuilders/easybuild-easyconfigs/pull/11101> Please advise! Kind regards, Rok
