Re: RFH: open-mpi
On Mon, Jan 09, 2006 at 04:49:12PM +0100, Florian Ragwitz wrote:
> Hello,
>
> I'm currently about to prepare openmpi Debian packages, but I experience
> the following problems with it:
>
> openmpi compiles various shared libraries (libopal, libmpi, libmpi_cxx,
> liborte, etc.) that don't make much sense when being used without
> openmpi.
So they should be probably be installed into /usr/lib/openmpi/, since
the compiletime linker doesn't need to be able to find them easily.
> Actually the orted utility and therefor liborte may be used without
> openmpi and the openmpi authors encourage users to do so, but there's no
> application at the moment that does this.
>
> I'm not sure how to handle the package(s) that will contain the openmpi
> libraries. Should I split it up in one package per shared library or is
> it a better way to put them all into a huge openmpi-libs package?
Is there any specific motivation to put them in a separate package?
The only reason I can think to do this, is to provide the libraries
without the application. But if the libraries aren't useful without
that application, then why bother?
I think that providing them in the same package is good where
possible, but the package name should reflect the SOversion (if they
are versioned), and if the libraries versions change at different
times, then this means that you have to have multiple SO runtime
packages.
This is documented as policy 8.1:
http://www.debian.org/doc/debian-policy/ch-sharedlibs.html
--
Clear skies,
Justin
Reply to: