Spack concretizer.yaml
Spack package manager concretizer.yaml config file
| Type | object |
|---|---|
| File match |
**/*spack/**/concretizer.yaml
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/spack-concretizer-yaml/latest.json |
| Source | https://raw.githubusercontent.com/spack/schemas/refs/heads/main/schemas/concretizer.json |
Validate with Lintel
npx @lintel/lintel check
Properties
Concretizer configuration that controls dependency selection, package reuse, and solver behavior
14 nested properties
Force re-concretization when concretizing environments
Controls how aggressively Spack reuses installed packages and build caches during concretization
Enable node namespace functionality in the concretizer
Controls which target microarchitectures are considered during concretization
2 nested properties
If true, only allow targets compatible with the current host; if false, allow any target (e.g., concretize for icelake while running on haswell)
Target selection granularity: 'microarchitectures' (e.g., haswell, skylake) or 'generic' (e.g., x86_64_v3, aarch64)
Controls whether environment specs are concretized together or separately
Whether to allow compiler mixing between link/run dependencies
Configuration for spec splicing: replacing dependencies with ABI-compatible alternatives to improve package reuse
2 nested properties
List of explicit splice configurations to replace specific dependencies
[]
Enable automatic splicing for ABI-compatible packages (experimental feature)
Controls whether the dependency graph can contain multiple configurations of the same package
2 nested properties
Duplication strategy: 'none' (single config per package), 'minimal' (allow build-tools duplicates), 'full' (experimental: allow full build-tool stack separation)
Maximum number of duplicates allowed per package when using strategies that permit duplicates
Enable static analysis to reduce concretization time by generating smaller ASP problems
Maximum time in seconds for the solve phase (0 means no time limit)
If true, timeout always results in error; if false, use best suboptimal solution found before timeout (yields unreproducible results)
Compatibility mapping between operating systems for reuse of compilers and packages (key: target OS, value: list of compatible source OSes)
Configuration for caching solver outputs from successful concretization runs
3 nested properties
Whether to utilize a cache of solver outputs from successful concretization runs
Path to the location where Spack will root the concretization cache
Limit on the number of concretization results that Spack will cache (0 disables pruning)
Configuration for how Spack handles external packages during concretization
1 nested properties
Controls how missing information (variants, etc.) is completed for external packages: 'architecture_only' completes only mandatory architectural information; 'default_variants' also completes missing variants using their default values