aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/config/numpy-scipy.cfg
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-08-08 22:48:53 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-08-08 22:56:07 +0100
commit09840874c3af449032a07cac56e23a78d7e3a666 (patch)
treebe19f1d9778cb7eb5ac3a16fd81ad8a6181bdf3c /reproduce/software/config/numpy-scipy.cfg
parentb3b44798a3f472e5f5a6633de4a582d4c902b008 (diff)
Software tarballs saved as symlinks if already in filesystem
Until now, if the software source tarballs already existed on the system they would be copied inside the project. However, the software source tarballs are sometimes/mostly larger than their actual product and can consume significant space (~375 MB in the core branch!). With this commit, when the software are present on the system, their symbolic link will be placed in 'BDIR/software/tarballs', not a full copy. Also, because the tarballs in software tarball directory may themselves be links, we use 'realpath' to find the final place of the actual file and link to that location. Therefore if 'realpath' can't be found (prior to installing Coreutils in Maneage), we will copy the tarballs from the given software tarball directory. After Maneage has installed Coreutils, the project's own 'realpath' will be used. Of course, if the software are downloaded, their full downloaded copy will be kept in 'BDIR/software/tarballs', nothing has changed in the downloading scenario.
Diffstat (limited to 'reproduce/software/config/numpy-scipy.cfg')
0 files changed, 0 insertions, 0 deletions