On 23/03/10 at 12:14 +0100, Thibaut Paumard wrote: > >Yes, it's probably better to just conflict in mpi-defaults with the > >other providers of mpicc. > > Which unfortunately forbids to both build with the default > implementation and with each available implementation. Agreed, this > is not recommended anyway. Just wondering if any package does this > already.
It doesn't make much sense to do that. If you want to do that, you should depend on libopenmpi-dev and libmpich2-dev directly. > >Note that help is usually welcomed. It might be better to invest > >time to > >solve that problem with a distribution-wide solution, rather than just > >for your own package. > > Which is why I am here discussing with you :-) I would be happy to > prepare a patch once the best solution is agreed. I'm not the mpi-defaults maintainer :-) Manuel? Adam? -- | Lucas Nussbaum | [email protected] http://www.lucas-nussbaum.net/ | | jabber: [email protected] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
