Skip to content
A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
Branch: develop
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE bug report template: suggest --stacktrace instead of -s (#10548) Feb 8, 2019
bin Fix typo in spack executable (#11512) May 19, 2019
etc/spack/defaults ninja: drop python as a run dep (#11347) May 7, 2019
lib/spack Make flake8 check spack script as well as .py files (#11513) May 20, 2019
share/spack junit: escape remaining inputs. (#11382) May 16, 2019
var/spack py-htseq: new version (#11525) May 21, 2019
.codecov.yml coverage: use kcov to get coverage for our cc script Dec 30, 2018
.coveragerc coverage: use kcov to get coverage for our cc script Dec 30, 2018
.dockerignore fix multiple issues with the docker images (#9718) Dec 20, 2018
.flake8 flake8: add exceptions for overly pedantic camelcase rules from pep8-… May 16, 2019
.flake8_packages flake8: add exceptions for overly pedantic camelcase rules from pep8-… May 16, 2019
.gitignore env: add spack env command, along with env.yaml schema and tests Nov 9, 2018
.mailmap Update for 'eccodes'. (#6604) Dec 8, 2017
.readthedocs.yml Updated Sphinx configuration (#11165) Apr 11, 2019
.travis.yml tests: stop testing Python 3.4 May 11, 2019
CODE_OF_CONDUCT.md Make CODE_OF_CONDUCT.md more Spack-specific (#11403) May 9, 2019
CONTRIBUTING.md relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE Oct 17, 2018
COPYRIGHT relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE Oct 17, 2018
LICENSE-APACHE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE Oct 17, 2018
LICENSE-MIT copyright: update license headers for 2013-2019 copyright. Jan 1, 2019
NOTICE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE Oct 17, 2018
README.md README: LLNL release number and SPDX id don't need to be monospaced. Jan 1, 2019

README.md

Spack Spack

Build Status codecov Read the Docs Slack

Spack is a multi-platform package manager that builds and installs multiple versions and configurations of software. It works on Linux, macOS, and many supercomputers. Spack is non-destructive: installing a new version of a package does not break existing installations, so many configurations of the same package can coexist.

Spack offers a simple "spec" syntax that allows users to specify versions and configuration options. Package files are written in pure Python, and specs allow package authors to write a single script for many different builds of the same package. With Spack, you can build your software all the ways you want to.

See the Feature Overview for examples and highlights.

To install spack and your first package, make sure you have Python. Then:

$ git clone https://github.com/spack/spack.git
$ cd spack/bin
$ ./spack install libelf

Documentation

Full documentation for Spack is the first place to look.

Try the Spack Tutorial, to learn how to use spack, write packages, or deploy packages for users at your site.

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, join the mailing list. We're using Google Groups for this:

Slack channel

Spack has a Slack channel where you can chat about all things Spack:

Sign up here to get an invitation mailed to you.

Twitter

You can follow @spackpm on Twitter for updates. Also, feel free to @mention us in in questions or comments about your own experience with Spack.

Contributions

Contributing to Spack is relatively easy. Just send us a pull request. When you send your request, make develop the destination branch on the Spack repository.

Your PR must pass Spack's unit tests and documentation tests, and must be PEP 8 compliant. We enforce these guidelines with Travis CI. To run these tests locally, and for helpful tips on git, see our Contribution Guide.

Spack uses 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 created by Todd Gamblin, tgamblin@llnl.gov.

Citing Spack

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

License

Spack is distributed under the terms of both the MIT license and the Apache License (Version 2.0). Users may choose either license, at their option.

All new contributions must be made under both the MIT and Apache-2.0 licenses.

See LICENSE-MIT, LICENSE-APACHE, COPYRIGHT, and NOTICE for details.

SPDX-License-Identifier: (Apache-2.0 OR MIT)

LLNL-CODE-647188

You can’t perform that action at this time.