Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] Improvement of openmpi.spec
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2009-08-06 10:14:56


On Aug 6, 2009, at 9:49 AM, Sylvain Jeaugey wrote:

> > -Source: openmpi-%{version}.tar.$EXTENSION
> > +Source: %{name}-%{version}.tar.$EXTENSION
> >
> > Does this mean that you're looking for a different tarball name?
> I'm not
> > sure that's good; the tarball should be an openmpi tarball,
> regardless of
> > what name it gets installed under (e.g., OFED builds an OMPI
> tarball 3-4
> > different ways [one for each compiler] and changes %name, but uses
> the same
> > tarball. How about another param (hey, we've got something like
> 100, so
> > what's 101? ;-) ) for the tarball that defaults to "openmpi"?
> They if you
> > want to have a differently-named tarball, you can.
> Well, maybe we could live with an openmpi tarball ... it was just to
> be
> consistent. When I build bullmpi-a.b.c.src.rpm, I somehow expect the
> tar
> file to be bullmpi-a.b.c.tar.gz.
>

I'm not opposed to having another variable to set the name of the
tarball if you want it.

-- 
Jeff Squyres
jsquyres_at_[hidden]