On Thu, 6 Aug 2009, Jeff Squyres wrote:
> -Source: openmpi-%{version}.tar.$EXTENSION
> +Source: %{name}-%{version}.tar.$EXTENSION
The spec file parser defines some of these variables by default. F.e.
after encountering at the top of the file:
Name: fftw
Version: 2.1.5
Release: 5.bc
somet
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
Hi Jeff,
Thanks for reviewing my changes !
On Thu, 6 Aug 2009, Jeff Squyres 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 openmp
Thanks! A few questions about this patch:
-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 ge
Hi all,
We had to apply a little set of modifications to the openmpi.spec file to
help us integrate openmpi in our cluster distribution.
So here is a patch which, as the changelog suggests, does a couple of
"improvements" :
- Fix a typo in Summary
- Replace openmpi by %{name} in a couple o
