Until very recently the BLAS library did not have any versioning.
We decided to synchronize the BLAS version with LAPACK.
Yes, indeed it makes sense to add the version number to the tgz.
I just updated the BLAS website to reflect the change.
let me know if you have any comments/questions
On Sep 27, 2015, at 2:45 PM, Todd Gamblin <tgamblin@Domain.Removed> wrote:
Hi netlib folks,
Some of us over at LLNL (along with collaborators) have been working on an
HPC package manager called Spack . Basically we're trying to encode
automatic, reproducible builds of HPC software, and LAPACK and BLAS are
fundamental pieces of this stack.
I have a small request. Would it be possible to version the tarball you post
for BLAS, similarly to the way LAPACK is done?
Right now, BLAS only has a single download , netlib.org/blas.tgz, for the
LAPACK, on the other hand, keeps links to old versions:
The tarballs have version numbers appended. Doing it this way allows our
tool to reliably download a particular version of BLAS, ensure that it
matches a checksum, and build it according to a saved specification.
Please let me know if it would be possible to change the BLAS tarball naming.
 Spack: https://github.com/scalability-llnl/spack/tree/develop.
Upcoming SC15 paper on the tool is attached.
Lapack mailing list
-------------- next part --------------
An HTML attachment was scrubbed...