298da8e2c4
* Add mising QE releases. * Update QE dependencies and conflicts. * QE 6.3 install method requires a patch to work properly. * include QE git develop branch * QE HDF5 needs Fortran support. HDF5 versions prior to 1.8.16 leads to QE runtime errors. * Number of MKL related conflicts for QE. * Flake8 fixes for QE for hdf5 lines. * Pass in all compilers properly to QE configure * Fixed external BLAS/LAPACK linkage in QE. * Library search was problematic in QE. * Add section headings to QE package. * External FFTW compatible libraries properly detected in QE. * Flake8 fixes for QE * QE configure defaults to False for ELPA, thus Spack package should as well. * QE depends on FFTW3 provider instead of FFTW explictly. * Primary QE repo is gitlab.com, not github.com. Github mirror lags behind gitlab site. * Support both 6.3-backports branch and develop branch in QE. * QE patch needed for proper MKL detection. MKL_ROOT is detected and preferred, still falls back to finding first MKL installation in /opt/intel. * Use FFTW-API provider versioned interface for specify QE FFT dependency. * QE FFTW conflicts no longer need thanks to FFTW-API provider versioned interface. * Flake8 3.6.0 fix in support of https://github.com/spack/spack/pull/9853 * Fix QE conflict with ilp64 variant in support of https://github.com/spack/spack/pull/9853 * Remove custom url_for_version for QE package and use builtin url instead. In support of https://github.com/spack/spack/pull/9853 * Use FFTW builtin flags for QE instead of custom Python code. In support of https://github.com/spack/spack/pull/9853 * Fix typo in QE package comments. In support of https://github.com/spack/spack/pull/9853 * Future proof QE package patches in anticipation of QE >= 6.3.1. In support of https://github.com/spack/spack/pull/9853 |
||
|---|---|---|
| .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