On Mon, 31 Mar 2014, Dimitri John Ledkov wrote:
The problem is that dependencies of the suggested packages are not multiarched, e.g. one cannot co-install libboost-mpi-python1.55-dev. I guess, there is more benefit to allow libboost1.55-dev be multiarched:same (since it's ready), even if all suggests are not multiarch installable. The libboost1.55-dev package is coinstallable across bitness and endianess different systems.
I was thinking of python (I hadn't checked) when I wrote "most", but indeed MPI may be an issue. However, those are exceptions, libboost-thread1.55-dev and many others have no problematic dependency.
Actually, is it really necessary to wait until all dependencies are multiarch-ready to mark a package? I don't think the content of libboost-mpi1.55-dev will change. If it was marked Multi-Arch: same, it would refuse to co-install because of missing dependencies, but would automatically work when openmpi is updated, no?
-- Marc Glisse -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
