#11576: mpich2 and openmpi both claim mpiexec(1) manpage --------------------------------+------------------------------------------- Reporter: stephen@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: mpi | Port: mpich2 openmpi hdf5-18 --------------------------------+------------------------------------------- Comment(by eborisch@…): Replying to [comment:13 stephen@…]:

If you're dead serious about that, one of the ports should be removed. Otherwise, there are use cases where one might use both (in particular, evaluating which one or the other not both you're going to use in production!)

I'm not sure where you're going here. The ticket was to resolve the collision between openmpi and mpich2. Solutions I can see: * We can declare them incompatible (mark them conflicting) and the "problem" goes away. If someone is evaluating one vs the other, they can (with minimal headache) activate one and then the other for testing. * If there is a real use case for keeping both installed, then we need to resolve the man page conflicts. I think man1 can be fixed as I described above with changes in openmpi. For the man3 pages, one of the ports will need to prevent them from installing for things to coexist. I'm happy to add a +man3 variant to mpich2 that can be disabled to permit co-existence. Thoughts? -- Ticket URL: <https://trac.macports.org/ticket/11576#comment:14> MacPorts <http://www.macports.org/> Ports system for Mac OS