ccce3b79ab
* SEACAS: Add preliminary support for seacas package * Eliminate leftover from package I copied from. * And remove another stray line Sorry, thought I had checked this better... * SEACAS: Shorten long lines; fixup indentation * SEACAS: Remove unused os import * Add PLASMA version 18.11.0 and Lua variant (#9689) * Add PLASMA 18.11.1 with optional Lua and test for headers * New versions for a few python modules (#9969) * py-jupyter-console: Add version 5.2.0 * py-jupyter-core: add version 4.4.0 * py-lxml: add version 4.2.5 * py-zmq: add version 17.1.2 * py-terminado: add version 0.8.1 * py-pexpect: add version 4.6.0 * py-pytables: add version 3.4.4 * SEACAS: Default to mpi on * SEACAS: Modify to reduce variants Instead of using an `allpkgs` or explicitly specifying each individual subset, changed to minimize variants: * By default, the exodus and IOSS libraries are built and a few executables directly related to the IOSS library. * variant `common` defaults to True and builds the "common" seacas applications. This is based on my definition, so there may be could be some discussion on what belongs here. * variant `legacy` defaults to True and builds the remainder of the seacas applications. These are still used, but mainly in more esoteric areas. Might be better to default to False, but I wanted default to just build everything which is what other SEACAS builds always do... Removed the `kokkos` variants for now as I need to do some more thinking on how best to support this. Not often used currently, so shouldn't be an issue. Cleaned up other issues raised by Adam and found by me. * SEACAS: Address flake8 issues * SEACAS: Clean up variant package logic Fixed package variant logic. Consolidated some other variant handling logic Other minor refactors for hopefully better readability * SEACAS: Fix flake8 error Missing whitespace around operator fixed. |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| var/spack | ||
| .codecov.yml | ||
| .coveragerc | ||
| .dockerignore | ||
| .flake8 | ||
| .flake8_packages | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| COPYRIGHT | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| NOTICE | ||
| 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.
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:
- 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.
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