Stefan Brüns writes:
On Mittwoch, 2. Januar 2019 22:36:52 CET Egbert Eich wrote:
This would be a nightmare. As I've stated elsewhere already, I believe it would be better if packages that are used by the 'naive' user - and especially their dependencies - should stay away from using any MPI. I don't see the benefit of MPI if you do not specifically set it up for your task. I will have to look at vtk - tomorrow probably.
The "serial" flavor, both in science and Factory, is ok now.
The openmpi(1) flavor is somewhat broken, as the dependency set for both openmpi1 and openmpi2 is imcomplete:
Only available as openmpi1:
- libnetcdf-openmpi, python3-mpi4py
I will take care of netcdf - once I've worked out the hdf5 issue.
Only available as openmpi2:
boost is on my list of packages anyway. I cannot promise when it will happen but I'd be happy to look into this as well.
So we have to fixup the dependencies first.
I have converted vtk to a multibuild package, see https://build.opensuse.org/ package/show/home:StefanBruens:branches:science/vtk
As openmpi2 is seems to available on all supported platforms (even PPC64BE since 2.1.4, science has 2.1.5), it should be a good default for everything not buildable with multiple flavors - probably only python.
Right. Nicolas also confirmed that this should work, so maybe we should go with this.
For vtk, this would mean adding an openmpi2 flavor to netcdf, and switching mpi4py to openmpi2.
Ok, lemme look into netcdf.