Package Details
| Package: |
bottleneck-0.7.0+3 |
| Product: |
bottleneck |
| SVN Revision: |
20928 |
| Effective SVN Revision (incl depedencies): |
28302 |
| Effective latest update: |
14/11/2014-10:49 |
| Lifecycle: |
operational |
| Lifecycle (spec): |
operational |
| State: |
OK |
| Validation State: |
OK |
| Inherited State: |
OK |
| Build State: |
OK |
| Test State: |
OK |
Dependency Graph
Remark: The dependency graph depicts for packages dependant on bottleneck-0.7.0+3 only the latest version per product. Furthermore, test dependencies are not visible.
Listed Dependencies (main)
For a list with all direct and indirect dependencies and dependants (main and test) see all dependencies.
Messages:
| OK |
Package validated, build and test status ok. |
All Reports
| build |
desbuild |
27/12/2014-18:58 |
OK |
Table File
| 1 |
setupRequired(numpy 1.6.2+7) |
| 2 |
setupRequired(python 2.7.6+0) |
| 3 |
setupRequired(scipy 0.11.0+6) |
| 4 |
setupRequired(nose 1.3.0+2) |
| 5 |
|
| 6 |
|
| 7 |
|
| 8 |
envPrepend(PYTHONPATH, ${PRODUCT_DIR}/lib/python2.7/site-packages) |
Build File
| 1 |
#!/usr/bin/env bash |
| 2 |
wget $EXTERNAL/$PRODUCT/$PRODUCT-$VERSION.tar.gz |
| 3 |
tar xzf $PRODUCT-$VERSION.tar.gz |
| 4 |
cd $PRODUCT-$VERSION |
| 5 |
|
| 6 |
# apparently setup needs numpy at build time, so we have to provide it |
| 7 |
# since it is part of the dependencies it has to be already installed |
| 8 |
if [ -z "$NUMPY_DIR" ] ; then setup numpy 1.6.2+4 ; fi |
| 9 |
|
| 10 |
python setup.py build |
| 11 |
|
| 12 |
mkdir -p ${PRODUCT_DIR}/lib/python2.7/site-packages |
| 13 |
export PYTHONPATH=$PRODUCT_DIR/lib/python2.7/site-packages:$PYTHONPATH |
| 14 |
python setup.py install --prefix=$PRODUCT_DIR |