Hi everyone, Years ago, work was started into 20-30 projects to allow complex matrix builds targeted for HPC users. The idea was to allow to build multiple versions of a libraries on top of multiple versions of their dependencies and so on. This was mostly used for libraries using MPI. A whole bunch of macros and overly complex bits of spec file code were added to these project so they could build against multiple versions of openmpi, mpich, mvapich, each with different versions of compilers. All these builds can then be installed at the same time on a system, letting the end user pick the "environment" right for his use case using lmod. That idea hasn't seem to really take off: - The spec file code is in each project is complex and messy due to spec file language restrictions and some OBS constraints - Maintenance is hellish because every time a new MPI package is added, *all* these projects needs to be manually updated by adding a _multibuild entry (easy enough), and expanding the pseudo switch/case that handles the build flavours to set the right variables. And of course many projects have a slight variation of that code to keep it fun :) Moreover, more and more HPC people are moving to Spack. While it may have its drawbacks, it makes it much easier to pick which libraries are to be compiled and installed in an "environment", without heavily tuning their spec files. Finally, SUSE had people working on this, but it is no longer the case. So as this is now an unmaintained, overly complex project, there are two ways out this: - Either there are enough users of these HPC builds, and one or more of them want to pick up maintainership over it. - Either we should disable these builds and drop the HPC support code completely from Factory. Nicolas Morey - RDMA/MPI maintainer