A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
Go to file
Todd Gamblin a1818f971f env: environments can be named or created in directories
- `spack env create <name>` works as before

- `spack env create <path>` now works as well -- environments can be
  created in their own directories outside of Spack.

- `spack install` will look for a `spack.yaml` file in the current
  directory, and will install the entire project from the environment

- The Environment class has been refactored so that it does not depend on
  the internal Spack environment root; it just takes a path and operates
  on an environment in that path (so internal and external envs are
  handled the same)

- The named environment interface has been hoisted to the
  spack.environment module level.

- env.yaml is now spack.yaml in all places.  It was easier to go with one
  name for these files than to try to handle logic for both env.yaml and
  spack.yaml.
2018-11-09 00:31:24 -08:00
.github/ISSUE_TEMPLATE fix numbering in build error template (#9030) 2018-08-21 12:37:24 -04:00
bin bugfix: work around ruamel.yaml vendoring issues (#9725) 2018-11-06 16:06:18 -08:00
etc/spack/defaults Allow setting language of compiler messages (#9486) 2018-10-18 12:55:58 -07:00
lib/spack env: environments can be named or created in directories 2018-11-09 00:31:24 -08:00
share/spack env: environments can be named or created in directories 2018-11-09 00:31:24 -08:00
var/spack utils: merge spack.environment into spack.util.environment 2018-11-09 00:31:24 -08:00
.codecov.yml Modulefiles generated with a template engine (#3183) 2017-09-19 12:34:20 -07:00
.coveragerc Restore multiprocessing in unit tests (#6949) 2018-01-20 16:10:25 +01:00
.dockerignore docker: unite Dockerfiles; auto-deploy images to DockerHub (#9329) 2018-10-26 10:15:05 -07:00
.flake8 flake8: explicitly allow line break before or after binary operator (#9627) 2018-10-25 15:11:22 -07:00
.flake8_packages flake8: explicitly allow line break before or after binary operator (#9627) 2018-10-25 15:11:22 -07:00
.gitignore env: add spack env command, along with env.yaml schema and tests 2018-11-09 00:31:24 -08:00
.mailmap Update for 'eccodes'. (#6604) 2017-12-08 09:34:37 +01:00
.travis.yml docker: allow docker build to fail until it's fixed (#9658) 2018-10-26 21:50:28 -07:00
CODE_OF_CONDUCT.md Add a code of conduct to Spack (#6251) 2017-11-09 21:18:58 -08:00
CONTRIBUTING.md relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
COPYRIGHT relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
LICENSE-APACHE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
LICENSE-MIT license: add copyright to MIT license and SPDX in README (#9645) 2018-10-26 00:49:35 -07:00
NOTICE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
README.md license: add copyright to MIT license and SPDX in README (#9645) 2018-10-26 00:49:35 -07:00

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