6dc8bbcb3a
* Updates to Mesa and other Xorg packages * Add packages for all Xorg Protocol extensions * Add packages for first half of Xorg libraries * Add packages for remaining Xorg libraries * Add packages for all Xorg utilities * Add packages for Xorg documentation tools * Add build deps to Xorg protocol headers * Add packages for XCB * Add build deps to Xorg libraries * Add build deps to Xorg utilities * Add packages for Xorg fonts and font-related utilities * Change font deptype from build to default I wasn't sure which deptype was appropriate at first since none of the packages are actually linked together. I initially chose the build deptype for this reason. However, the font packages don't install into their own prefix. They install into font-config. If font-config is a build dependency, that means you can uninstall it without uninstalling the font packages, which wouldn't make sense since they install into font-config. So I switched them back to the default deptype. * Minor formatting changes to ncview * Add half-way done xorg-server package * Add packages for Xorg test suites, not yet tested! * Add packages for Xorg data * Add first quarter of Xorg apps * Add more packages for Xorg apps * Add dependencies to mesa * Remove comments from mesa package * Flake8 * Add more packages for Xorg apps * Add more packages for Xorg apps * Add more packages for Xorg apps * Add more packages for Xorg apps * Add more packages for Xorg apps * Add package for Sublime Text * Add packages for remaining Xorg apps * Revisit testing packages, add missing dependencies * Add dependencies, clean up FIXMEs |
||
|---|---|---|
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| var/spack | ||
| .coveragerc | ||
| .flake8 | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| LICENSE | ||
| README.md | ||
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:
- 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, the first step is to join the mailing list. We're using a Google Group for this, and you can join it here:
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.
Before you send a PR, your code should pass the following checks:
-
Your contribution will need to pass the
spack testcommand. Run this before submitting your PR. -
Also run the
share/spack/qa/run-flake8-testsscript to check for PEP8 compliance. To encourage contributions and readability by a broad audience, Spack uses the PEP8 coding standard with a few exceptions.
We enforce these guidelines with Travis CI.
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 originally written 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 LICENSE file.
LLNL-CODE-647188