[Paraview] Fedora mpi packaging

[Orion Poplawski]

I'm the packager for the Fedora paraview package.  Currently I've been 
making "normal" and "mpi" packages compiled without and with openmpi 
support respectively.  Currently the mpi version is busted and I'm 
working on fixing it with the help of Tyson Whitehead who filed a 
helpful bug: https://bugzilla.redhat.com/show_bug.cgi?id=450598

My current question is what binaries need mpi versions?  Just about 
everything ends up with openmpi dependencies:

/usr/bin/paraview-mpi
         libmpi_cxx.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi_cxx.so.0 
(0x00002aaab0235000)
         libmpi.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi.so.0 
(0x00002aaab0457000)
         libopen-rte.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-rte.so.0 (0x00002aaab06eb000)
         libopen-pal.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-pal.so.0 (0x0000003f2e600000)
/usr/bin/pvTestDriver-mpi
/usr/bin/pvbatch-mpi
         libmpi_cxx.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi_cxx.so.0 
(0x00002aaab3abf000)
         libmpi.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi.so.0 
(0x00002aaab3ce1000)
         libopen-rte.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-rte.so.0 (0x00002aaab3f75000)
         libopen-pal.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-pal.so.0 (0x0000003f2e600000)
/usr/bin/pvdataserver-mpi
         libmpi_cxx.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi_cxx.so.0 
(0x00002aaab3d4f000)
         libmpi.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi.so.0 
(0x00002aaab3f72000)
         libopen-rte.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-rte.so.0 (0x00002aaab4205000)
         libopen-pal.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-pal.so.0 (0x0000003f2e600000)
/usr/bin/pvpython-mpi
         libmpi_cxx.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi_cxx.so.0 
(0x00002aaab3abf000)
         libmpi.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi.so.0 
(0x00002aaab3ce1000)
         libopen-rte.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-rte.so.0 (0x00002aaab3f75000)
         libopen-pal.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-pal.so.0 (0x0000003f2e600000)
/usr/bin/pvrenderserver-mpi
         libmpi_cxx.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi_cxx.so.0 
(0x00002aaab3d4f000)
         libmpi.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi.so.0 
(0x00002aaab3f72000)
         libopen-rte.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-rte.so.0 (0x00002aaab4205000)
         libopen-pal.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-pal.so.0 (0x0000003f2e600000)
/usr/bin/pvserver-mpi
         libmpi_cxx.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi_cxx.so.0 
(0x00002aaab3d4f000)
         libmpi.so.0 => /usr/lib64/openmpi/1.2.4-gcc/libmpi.so.0 
(0x00002aaab3f72000)
         libopen-rte.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-rte.so.0 (0x00002aaab4205000)
         libopen-pal.so.0 => 
/usr/lib64/openmpi/1.2.4-gcc/libopen-pal.so.0 (0x0000003f2e600000)

But I'm guessing you could use a non-mpi "paraview" binary to connect to 
  a parallel running pvserver just fine.  Does it make sense to ship mpi 
versions of these other binaries?

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  orion at cora.nwra.com
Boulder, CO 80301              http://www.cora.nwra.com