Add new mpi provider for mpi-serial about mpi-feedstock HOT 7 CLOSED

@ocefpaf, @minrk and @leofang, do you have thoughts on this?

I would suggest mpi-serial over just serial, though that means the build strings for dependencies would be mpi_mpi-serial..., which would be odd.

My group really would benefit from having a solution to this (a working nompi version of ESMF sepecifically) by July or so, so it would be really helpful if we can make some headway now. It seems like the process of adding mpi-serial might be fairly involved.

from mpi-feedstock.

I don't have objection here. mpi-serial is better as it reflects the package name; serial would be causing confusion when this propagates to downstream recipes.

from mpi-feedstock.

Should we ping core as well?

from mpi-feedstock.

@conda-forge/core, if anyone is interested and has time to engage on this issue, please do. We would benefit from any advice before we get started adding a new MPI implementation.

from mpi-feedstock.

I would suggest mpi-serial over just serial, though that means the build strings for dependencies would be mpi_mpi-serial..., which would be odd.

According to https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html#build-section:

The build string cannot contain "-".

So we would need to define this as mpi_serial rather than mpi-serial and build strings will be mpi_mpi_serial....

from mpi-feedstock.

@conda-forge/core, if anyone is interested and has time to engage on this issue, please do. We would benefit from any advice before we get started adding a new MPI implementation.

I think @ocefpaf is a core dev and he already gave his thumbs up above 🙂

from mpi-feedstock.

@leofang, thanks, that's a good point. @ocefpaf, is there anyone else from core you'd want to have a look? It looks like @isuruf is already taking a look at things so that's very helpful!

from mpi-feedstock.