The Spack package manager: bringing order to HPC software chaos

By T. Gamblin, M. LeGendre, M. Collette, Gregory L. Lee, A. Moody, Bronis R. de Supinski, S. Futral. International Conference for High Performance Computing, Networking, Storage and Analysis, 2015

355 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Hardware and Architecture, Information Systems and Management

View Paper: https://www.semanticscholar.org/paper/b80cb14c69b8201e0f1e5554549e7820da6e337b

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Hardware and Architecture

1. Wolfgang Bangerth
2. Timo Heister

Citations in the corpus

• The deal.II finite element library: Design, features, and insights (2019, methodology): “Thus, users are required to install these external projects by hand, rely on pre-installed versions made available by their system administrators, or use tools that facilitate building scientific software such as Spack [69].”
• LLMs as Packagers of HPC Software (2025, unknown): “In this paper, we use the Spack [12] package manager to model relationships between independent software components, execute installation logic, and evaluate whether automatically generated build specifications can be used to install software.”