I observed today that many packages which can use MPI demand directly openpmi library instead of virtual/mpi (e.g. vtk, boost). So the question arises what is the reason for virtual/mpi if only one library for message passing have to be installed anyway. Actually this situation prevents us from using for example mpich2, because different MPI implementations block each other. Is this possible to demand in ebuilds for boost, vtk, etc. just virtual/mpi? If not let's remove it from potage just to not pretend we have a choice for MPI library. Reproducible: Always
*** This bug has been marked as a duplicate of bug 309365 ***