Spack config.yaml
Spack package manager config.yaml file
| Type | object |
|---|---|
| File match |
**/*spack/**/config.yaml
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/spack-config-yaml/latest.json |
| Source | https://raw.githubusercontent.com/spack/schemas/refs/heads/main/schemas/config.json |
Validate with Lintel
npx @lintel/lintel check
Properties
Spack's basic configuration options
{}
36 nested properties
Build flag configuration options
1 nested properties
Whether to keep -Werror flags active in package builds
Control how shared libraries are located at runtime on Linux
Installation tree configuration
3 nested properties
The location where Spack will install packages and their dependencies
Length to pad installation paths to allow better relocation of binaries (true for max length, integer for specific length)
Customize directory structure and naming schemes by mapping specs to format strings.
1 nested properties
Default projection format string used as fallback for all specs that do not match other entries. Uses spec format syntax like "{name}/{version}/{hash:16}".
Length of hash used in installation directory names
Temporary locations Spack can try to use for builds
Name format for build stage directories
Name for development spec build stage directories
Directory in which to run tests and store test results
List of Spack extensions to load
Locations where templates should be found
Directory where licenses should be located
Location to cache downloaded tarballs and repositories
Temporary directory to store long-lived cache files, such as indices of packages
Directory where Spack managed environments are created and stored
Abort downloads after this many seconds if no data is received (0 disables timeout)
When true, Spack will verify certificates of remote hosts when making SSL connections
Path to custom certificates for SSL verification
Suppress GPG warnings from binary package verification
Enable debug mode for additional logging
When true, Spack verifies downloaded source code using checksums
If true, Spack will fetch deprecated versions without warning
When true, concurrent instances of Spack will use locks to avoid conflicts (strongly recommended)
When true, builds will NOT clean potentially harmful variables from the environment
The language the build environment will use (C for English, empty string for user's environment)
The maximum number of jobs to use for the build system (e.g. make -j), defaults to 16
The maximum number of concurrent package builds a single Spack instance will run
When true, Spack's compiler wrapper will use ccache when compiling C and C++
How long to wait to lock the Spack installation database
How long to wait when attempting to modify a package (null for never timeout)
Allow installation on filesystems that don't allow setgid bit manipulation
Whether to show status information in the terminal title during the build
The default URL fetch method to use (urllib or curl)
Additional paths to search for external packages
Number of seconds a buildcache's index.json is cached locally before probing for updates
A mapping of aliases that can be used to define new Spack commands
Which installer to use. The new installer is experimental.