Draft:Spack (package manager)
 | Draft article not currently submitted for review.
This is a draft Articles for creation (AfC) submission. It is not currently pending review. While there are no deadlines, abandoned drafts may be deleted after six months. To edit the draft click on the "Edit" tab at the top of the window. To be accepted, a draft should:
It is strongly discouraged to write about yourself, your business or employer. If you do so, you must declare it. Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Last edited by UtherSRG (talk | contribs) 3 seconds ago. (Update) |
| Initial release | July 9, 2014[1] |
|---|---|
| Stable release | 0.21.1[2]
/ January 11, 2024 |
| Written in | Python |
| Platform | aarch32, aarch64, ppc, ppcle, ppc64, ppc64le, riscv64, sparc, sparc64, x86, x86-64 |
| Type | Package management |
| License | MIT and Apache 2.0 |
| Website | spack |
Spack is the Supercomputing Package manager tool developed at the Lawrence Livermore National Laboratory (LLNL) to manage the combinatorial complexity of scientific software[3]. Spack allows users to compose packages parameterized by version, platform, compiler, options, and dependency packages using a specification syntax or spec. An installed spec is available as an environmental module that can be loaded and unloaded as part of a traditional high-performance computing (HPC) workflow. Unlike environmental modules traditionally created by system administrators, however, spack ensures reproducibility by storing all python package recipes used to build the software, including output build log and environment files. Additionally, users can setup spack simply by cloning the spack git repository and therefore need not rely on an existing, shared spack installation.
See also
[edit]References
[edit]- ^ "Release v0.8 (2014-07-09) · spack/spack". GitHub.
- ^ "Release v0.21.1 (2024-01-11) · spack/spack". GitHub.
- ^ Gamblin, Todd; LeGendre, Matthew P.; Collette, Michael R.; Lee, Gregory L.; Moody, Adam; de Supinski, Bronis R.; Scott Futral, W. The Spack package manager: bringing order to HPC software chaos (PDF). Supercomputing 2015 (SC15). Austin, Texas. doi:10.1145/2807591.2807623.