Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-25 Thread Manuel Prinz
Am Donnerstag, den 25.03.2010, 18:28 +0100 schrieb Thibaut Paumard: > No, with the prioriy of OpenMPI raised above that of MPICH2, and with > the idea of switching from LAM to MPICH2 on the other arches, my patch > does not bring any _immediate_ benefit. It's a proposal for a longer > term so

Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-25 Thread Thibaut Paumard
Hi Manuel, Le 25 mars 10 à 18:07, Manuel Prinz a écrit : So, given that the priority in Open MPI changed and we will transition, do you think the patch is useful? I do not refrain from applying it to mpi-default but my understanding is that we do not need to have it as of now. No, with t

Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-25 Thread Manuel Prinz
Hi Thibaut, thanks for clarifying! It seems to me that we share the same opinion in (almost) all points but have a different view on the topic. Am Donnerstag, den 25.03.2010, 16:57 +0100 schrieb Thibaut Paumard: > Installing mpicc.default as an alternative is to make sure the default > implemen

Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-25 Thread Thibaut Paumard
Le 25 mars 10 à 14:30, Manuel Prinz a écrit : But there is still one thing I do not get: What problem is solved by installing mpicc.default as alternative? If the sysadmin did change the MPI implementation via update-alternatives, it will stay that way. It has no benefit over simply providin

Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-25 Thread Manuel Prinz
> Le 24 mars 10 à 16:59, Lucas Nussbaum a écrit : > > Actually, the information I was missing is that some packages depend > > on > > mpi-default-dev. I thought that mpi-default-dev was only used as a > > build-dependency. In that case, conflicting is indeed harmful, so the > > only solution is t

Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-25 Thread Thibaut Paumard
Le 24 mars 10 à 16:59, Lucas Nussbaum a écrit : Several solutions were [2]discussed. The easiest and most robust is to conflict with all the non-default implementations of mpi-dev. A smoother solution is to provide links like "mpicc.default" pointing to the right implementation, and instal

Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-24 Thread Lucas Nussbaum
On 24/03/10 at 16:20 +0100, Thibaut Paumard wrote: > Package: mpi-default-dev > Version: 0.6 > Severity: normal > Tags: patch > > As discussed on [1]debian-science, the way mpi-default-dev works > does not ensure > that the right MPI implementation is used. For instance, if > libmpich2-dev is > i

Bug#575259: mpi-default-dev doesn't ensure that the right implementation is used

2010-03-24 Thread Thibaut Paumard
Package: mpi-default-dev Version: 0.6 Severity: normal Tags: patch As discussed on [1]debian-science, the way mpi-default-dev works does not ensure that the right MPI implementation is used. For instance, if libmpich2- dev is installed on the system, it will _always_ be used by default becaus