packaging mpich2 -- conflicts with lam and file layoutb

[Enrico Scholz]

ed at eh3.com (Ed Hill) writes:

> I want multiple MPI implementations installed side-by-side and I
> want to select, for instance, which "mpirun" is called on a ***
> per-session basis *** by either specifying its full path or by using
> some semi-automated ${PATH} manipulation magic such as:
> ...
> So, my question for the packaging-gurus becomes:  Is there some way that
> we can accomplish that using something like (that is, similar but
> perhaps not exactly the same as):
>
>   /usr/lib/${MPI_IMPL_NAME}/{bin,man,lib,include}

You could create binaries like

| /usr/bin/lam-mpiCC
| /usr/bin/mpich2-mpiCC

These binaries are settings correct $PATHs (resp. this should not be
needed when the packages are configured with correct paths).

In simplest case, the binaries are sym- or hardlinks like

/usr/bin/mpich2-mpiCC -> ../lib/mpich2/bin/mpiCC

or small C programs (linked against dietlibc to speedup the start). They
should not shell scripts because this would add a noticable performance
impact.


The binaries can be linked with 'alternatives' to the common '/usr/bin/mpi*'
name but users can address their prefered implementation by specifying the
mpi compiler directly.


Obviously, this does not solve the conflicts-with-core issue because
'lam' must be changed in this way also.




Enrico
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 480 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-extras-list/attachments/20051108/b949eae0/attachment.sig>