Clone of the official spack repository with modifications for HLRS HAWK
Find a file
2016-03-22 19:18:04 +01:00
bin Fix #104, #54: issues with overlong shebang in deep directories. 2016-03-05 04:18:48 -08:00
etc/spack Add default repos.yaml 2015-11-28 19:11:51 -08:00
lib/spack Change from PR #552: rename setup_dependent_python_module -> setup_dependent_package 2016-03-22 01:56:16 -07:00
share/spack Support Bash "-u" mode 2016-03-19 18:42:39 -04:00
var/spack/repos temporary fix Hypre for OSX by building static lib by default 2016-03-22 19:18:04 +01:00
.gitignore Rework Spack config: keep user & site config in memory. 2015-12-25 14:00:33 -08:00
.mailmap Update mailmap 2016-02-03 11:47:48 -07:00
.travis.yml Add compiler info and a simple libdwarf build to the checks. 2016-03-15 14:33:10 -07:00
LICENSE Update README.md and LICENSE with new github.com/llnl URLs 2015-12-09 01:10:14 -08:00
README.md Updated links to use new llnl.gov address 2016-02-28 19:47:19 -08:00

image

Build Status

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 written 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 https://github.com/llnl/spack.git
$ cd spack/bin
$ ./spack install libelf

Documentation

Full documentation for Spack is the first place to look.

See also:

Get Involved!

Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, or even new core features.

Mailing list

If you are interested in contributing to spack, the first step is to join the mailing list. We're using a Google Group for this, and you can join it here:

Contributions

At the moment, contributing to Spack is relatively simple. Just send us a pull request. When you send your request, make develop the destination branch.

Spack is using a rough approximation of the Git Flow branching model. The develop branch contains the latest contributions, and master is always tagged and points to the latest stable release.

Authors

Many thanks go to Spack's contributors.

Spack was originally written by Todd Gamblin, tgamblin@llnl.gov.

Citing Spack

If you are referencing Spack in a publication, please cite the following paper:

Release

Spack is released under an LGPL license. For more details see the LICENSE file.

LLNL-CODE-647188