5727054c4a
* Support pruning of vars with Env from_sourcing_file (issue #6501) - Blacklist string literals or regular expressions of environment variables that are to be removed from consideration as being affect by the sourcing of the file. Conversely, whitelist modifications that should not ignored. Whitelisted variables have priority over blacklisting. Eg, EnvironmentModifications.from_sourcing_file ( bashrc blacklist=['JUNK_ENV', 'OPTIONAL_.*'], whitelist=['OPTIONAL_REQUIRED.*'] ) This modification can be used to eliminate environment variables that are not generalized for modules (eg, user-specific variables). * BUG: module prepend-path in wrong order (fixes #6501) * STYLE: module variables in sorted order (issue #6501) - looks nicer and also helps when comparing the contents of different module files. * ENH: remove duplicates from env paths when creating modules (issue #6501) - this makes for a cleaner module environment and helps avoid some unnecessary changes to the environment that are only provoked by redundancies in the PATH. eg, before PATH=/usr/bin after PATH=/usr/bin:/usr/bin:/my/application/bin should only result in /my/application/bin being added to the PATH and not /usr/bin:/my/application/bin Activate via the 'clean' flag (default: False): EnvironmentModifications.from_sourcing_file(bashrc, clean=True,.. |
||
|---|---|---|
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| templates/modules | ||
| var/spack | ||
| .codecov.yml | ||
| .coveragerc | ||
| .flake8 | ||
| .flake8_packages | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| issue_template.md | ||
| LICENSE | ||
| NOTICE | ||
| pytest.ini | ||
| README.md | ||
Spack
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:
- Technical paper and slides on Spack's design and implementation.
- Short presentation from the Getting Scientific Software Installed BOF session at Supercomputing 2015.
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.
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:
- Todd Gamblin, Matthew P. LeGendre, Michael R. Collette, Gregory L. Lee, Adam Moody, Bronis R. de Supinski, and W. Scott Futral. The Spack Package Manager: Bringing Order to HPC Software Chaos. In Supercomputing 2015 (SC’15), Austin, Texas, November 15-20 2015. LLNL-CONF-669890.
Release
Spack is released under an LGPL license. For more details see the NOTICE and LICENSE files.
LLNL-CODE-647188