Chris Coutinho writes:
For what it's worth, I use `mpi-selector` to set a system-wide MPI implementation and then switch between them. This keeps MPI libraries from clashing when I build software from source.
I'm not sure if the openSUSE packages use this method, but it works for packages I build myself really well. Are you building hdf5 and/or netcdf yourself?
Yeah, this is actually the intended approach. The problem comes in if a user installs package 'A' which requires package 'B' which in turn requires openmpi2 (for instance): the user may not even be aware of what MPI is and how it is intended to be used.