packaging mpich2 -- conflicts with lam and file layoutb

[Ed Hill]

On Tue, 2005-11-08 at 11:31 -0500, Ed Hill wrote:
> On Tue, 2005-11-08 at 15:39 +0000, Paul Howarth wrote:
> > Ed Hill wrote:
> > > Thanks for the feedback!  And can someone please explain how the
> > > alternatives thing works or, even better, point me towards a doc that
> > > explains it?
> > 
> > "man alternatives" is a start, and you might also look at the spec files 
> > for sendmail and postfix, which provide alternative MTAs using the 
> > alternatives system.
> 
> Thanks, Paul!
> 
> So, reading the man pages, alternatives boils down to a bunch of
> symbolic links.  Well, that stinks (tm).  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:
> 
>   http://modules.sourceforge.net/
> 
> as discussed at:
> 
>   https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171993
> 
> 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}
> 
> that will be acceptable wrt the Fedora packaging guidelines and, if
> necessary, the FHS as well?  Is it even possible?  And, if so, how?

Hi folks,

The above email sounds kinda demanding and, after re-reading it, I want
to emphasize that I'm humbly begging for the above functionality.

Please, please, please...  ;-)

Ed

-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Rm 54-1424;  77 Massachusetts Ave.
             Cambridge, MA 02139-4307
emails:  eh3 at mit.edu                ed at eh3.com
URLs:    http://web.mit.edu/eh3/    http://eh3.com/
phone:   617-253-0098
fax:     617-253-4464