50f74c117e
The dependency hash wasn't being generated in a consistent way: when read from .spec file in the install directory, the spec DAG was not normalized, but when generated on install, it was. Thus the same spec can have two possible hashes, which is obviously not good. In this commit: - Added a dep_hash function to spec, which should be used to get the dependency hash in all cases. This function normalizes the spec before generating the hash. - removed sha1 functions from Spec and DependencyHash. The one on Spec is not needed and is confusing (it hashed the whole spec, not just hash the deps) and the one on DependencyHash wasn't guaranteed to be safe because it can't normalize its parent spec before hashing. Hopefully this makes things consistent and easy.
Spack
Spack is a package management tool designed to support multiple versions and configurations of software on a wide variety of platforms and environments. It was designed for large supercomputing centers, where many users and application teams share common installations of software on clusters with exotic architectures, using libraries that do not have a standard ABI. Spack is non-destructive: installing a new version does not break existing installations, so many configurations can coexist on the same system.
Most importantly, Spack is simple. It offers a simple spec syntax so that users can specify versions and configuration options concisely. Spack is also simple for package authors: package files are writtin in pure Python, and specs allow package authors to write a single build script for many different builds of the same package.
See the Feature Overview for examples and highlights.
To install spack and install your first package:
$ git clone git@github.com:scalability-llnl/spack.git
$ cd spack/bin
$ ./spack install libelf
Documentation
Full documentation for Spack is also available.
Authors
Spack was written by Todd Gamblin, tgamblin@llnl.gov. LLNL-CODE-647188