On Tue, Dec 01, 2009 at 03:49:20PM +1100, Drew Parsons wrote: > I understand the final state of the modern Debian infrastructure for MPI > is now in place (modulo the questions around deprecating MPICH and LAM). > That is, the disruptive Open MPI transition is now complete, correct?
Yes, so far as I know. There might be the occasional need for a binNMU as MPICH2 settles in and if mpi-default-dev switches to MPICH2 instead of LAM as the backup, but those shouldn't interfere with testing migration. > >From the point of view of a client package, what is now best practice > for working with MPI? Is there a website/wiki/document explaining how > to set up an MPI-using package, or is it just a matter of RTFM from > mpi-default-dev? > > For context, gerris includes MPI support which is currently switched > off. I would like to create an additional gerris-mpi package which has > MPI switched on. No particular documentation that I'm aware of, though it's a good thought.... If you just want one MPI package, it should be enough to Build-Depend on mpi-default-dev and perform a build of your package with whatever flags are necessary -- which ideally should be something simple like "configure --enable-mpi CC=mpicc". -- Nicholas Breen nbr...@ofb.net -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org