Hummm... I guess I am totally confused and talking from a weak position of deep ignorance of the overall packaging.
I can happily see that the MPI stuff should not be in the default set of Boost things drawn in: Boost MPI is a specialist thing and so should be individually brought in on an as need basis. However what I thought I saw and reported was that there is an inconsistency with the packages libboost*mpi*, i.e. the packages that are specifically labelled as MPI related, in Ubuntu.
From what I can see libboost-mpi-dev is in Debian Sid and points to libboost-mpi1.42-dev.
It may be that this is just miscommunication and there is no conflict. Lucid I guess is now history and cannot be changed. Looking forward to Maverick, having libboost-mpi-dev must be considered essential referring to libboost-mpi1.42-dev or (preferably) later.
Fabrice,
Hummm... I guess I am totally confused and talking from a weak position of deep ignorance of the overall packaging.
I can happily see that the MPI stuff should not be in the default set of Boost things drawn in: Boost MPI is a specialist thing and so should be individually brought in on an as need basis. However what I thought I saw and reported was that there is an inconsistency with the packages libboost*mpi*, i.e. the packages that are specifically labelled as MPI related, in Ubuntu.
From what I can see libboost-mpi-dev is in Debian Sid and points to libboost- mpi1.42- dev.
It may be that this is just miscommunication and there is no conflict. Lucid I guess is now history and cannot be changed. Looking forward to Maverick, having libboost-mpi-dev must be considered essential referring to libboost- mpi1.42- dev or (preferably) later.