Re: ITP: mpi-defaults -- Meta-packages depending on appropriate MPI -dev and -bin packages for each platform

Gerber van der Graaf <[email protected]>
Newsgroups gmane.linux.debian.science,gmane.linux.debian.devel.beowulf
Message-ID <[email protected]>
Now I can put dependencies of the newer release of my packages against
mpi-default-*. Actually, I even would prefer this as a permanent
solution instead of a temporary one. No bothering anymore about openmpi/
lam/mpich or whatsoever.

Gerber

On Fri, 2008-12-26 at 01:01 -0500, Adam C Powell IV wrote:
> On Thu, 2008-11-20 at 09:45 -0500, Adam C Powell IV wrote:
> > On Thu, 2008-11-20 at 12:35 +0100, Ondrej Certik wrote:
> > > On Thu, Nov 20, 2008 at 11:14 AM, Manuel Prinz
> > <[email protected]> wrote:
> > > > Am Mittwoch, den 19.11.2008, 09:05 -0600 schrieb Dirk
> > Eddelbuettel:
> > > >> I think we should put either debian or mpi first. How about
> > > >>
> > > >>           mpi-default-{dev,bin}
> > > >>
> > > >> or even
> > > >>
> > > >>           mpi-debian-default-{dev,bin}
> > > >>
> > > >> to make it even clearer that it is just 'us' (ie Debian) defining a default
> > > >> for us, rather misconstruing that more than two decades (I'm guessing) of
> > > >> competing mpi implementations have ended ? ;-)
> > > >
> > > > Good guessing. But I'm confident we can solve that problem in one way or
> > > > another in a shorter time frame.
> > > >
> > > >> Comments ?
> > > >
> > > > Well, why not debian-default-mpi-{bin,dev}? ;)
> > > >
> > > > Seriously, I do not care that much. A name is a name. If we're lucky,
> > > > the package might be gone by release of Squeeze.
> > > 
> > > I like Dirk's suggestion more:
> > > 
> > >          mpi-default-{dev,bin}
> > > 
> > > But as you said, a name is just a name.
> > 
> > I like this suggestion, and have just posted the new package for comment
> > in the alioth debian-science repository:
> > git://git.debian.org/git/debian-science/packages/mpi-defaults.git
> > http://git.debian.org/?p=debian-science/packages/mpi-defaults.git;a=summary
> > 
> > It uses the PETSc system, which Build-Depends on an arch-dependent MPI
> > implementation, then rules uses readlink to determine which one is the
> > default alternative, and sets substvars appropriately, whether openmpi,
> > lam, or mpich*.  That way, if we want to change the defaults, we just
> > need to change the Build-Depends in control.  In many other ways it
> > follows the example of java-common.
> 
> This was just accepted!  Yay!  I'm now wishist bugging all of my
> packages to use it, and will start uploading with hypre tonight.
> 
> -Adam
-- 
Gerber van der Graaf
GnuPG key fingerprint: 
BF0A BBFE 5623 9761 C9E1 7C82 8B08 F586 D39A 2B64
http://gpiv.sourceforge.net/


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.