| 1 |
< |
### RPM external rivet 1.3.0 |
| 1 |
> |
### RPM external rivet 1.4.0 |
| 2 |
|
Source: http://www.hepforge.org/archive/rivet/Rivet-%{realversion}.tar.gz |
| 3 |
+ |
|
| 4 |
|
Requires: hepmc boost fastjet swig gsl |
| 5 |
+ |
Patch0: rivet-1.4.0 |
| 6 |
|
%prep |
| 7 |
|
%setup -n Rivet-%{realversion} |
| 8 |
< |
./configure --prefix=%i --with-boost=${BOOST_ROOT} --with-hepmc=$HEPMC_ROOT --with-fastjet=$FASTJET_ROOT --with-gsl=$GSL_ROOT --disable-doxygen --disable-pdfmanual --disable-pyext --with-pic |
| 8 |
> |
%patch0 -p0 |
| 9 |
> |
./configure --prefix=%i --with-boost=${BOOST_ROOT} --with-hepmc=$HEPMC_ROOT --with-fastjet=$FASTJET_ROOT --with-gsl=$GSL_ROOT --disable-doxygen --disable-pdfmanual --with-pic |
| 10 |
> |
# The following hack insures that the bins with the library linked explicitly |
| 11 |
> |
# rather than indirectly, as required by the gold linker |
| 12 |
> |
perl -p -i -e "s|LIBS = $|LIBS = -lHepMC|g" bin/Makefile |
| 13 |
|
%build |
| 14 |
|
make |
| 15 |
|
%install |
| 16 |
|
make install |
| 17 |
< |
# SCRAM ToolBox toolfile |
| 18 |
< |
mkdir -p %i/etc/scram.d |
| 19 |
< |
cat << \EOF_TOOLFILE >%i/etc/scram.d/rivet.xml |
| 20 |
< |
<tool name="rivet" version="%v"> |
| 15 |
< |
<lib name="rivet"/> |
| 16 |
< |
<client> |
| 17 |
< |
<environment name="RIVET_BASE" default="%i"/> |
| 18 |
< |
<environment name="LIBDIR" default="$RIVET_BASE/lib"/> |
| 19 |
< |
<environment name="INCLUDE" default="$RIVET_BASE/include"/> |
| 20 |
< |
<environment name="PDFPATH" default="$RIVET_BASE/share"/> |
| 21 |
< |
</client> |
| 22 |
< |
<runtime name="PATH" value="$RIVET_BASE/bin"/> |
| 23 |
< |
<runtime name="LD_LIBRARY_PATH" value="$RIVET_BASE/lib"/> |
| 24 |
< |
<runtime name="PYTHONPATH" value="$RIVET_BASE/lib/python2.6/site-packages"/> |
| 25 |
< |
<runtime name="RIVET_ANALYSIS_PATH" value="$RIVET_BASE/lib"/> |
| 26 |
< |
</tool> |
| 27 |
< |
EOF_TOOLFILE |
| 28 |
< |
%post |
| 29 |
< |
%{relocateConfig}etc/scram.d/rivet.xml |
| 17 |
> |
# The following creates a (for now) empty directory consistent with the |
| 18 |
> |
# tool definition (probably the PYTHONPATH entry could be removed there, |
| 19 |
> |
# too, but I'm still not sure if there is a use case for the python or not) |
| 20 |
> |
mkdir -p %i/lib/python2.6/site-packages |
