new_installer.py: implement --use-buildcache, --cache-only, --use-cache and --only#51593
Merged
new_installer.py: implement --use-buildcache, --cache-only, --use-cache and --only#51593
--use-buildcache, --cache-only, --use-cache and --only#51593Conversation
Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Harmen Stoppels <[email protected]>
Signed-off-by: Harmen Stoppels <[email protected]>
haampie
changed the title
--use-buildcache, --cache-only, --use-cache and --only
Signed-off-by: Harmen Stoppels <[email protected]>
alalazo
previously approved these changes
Nov 18, 2025
Signed-off-by: Harmen Stoppels <[email protected]>
alalazo
approved these changes
Nov 18, 2025
31 tasks
psakievich
pushed a commit
to psakievich/spack
that referenced
this pull request
Dec 1, 2025
…e-cache` and `--only` (spack#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]>
becker33
pushed a commit
that referenced
this pull request
Jan 11, 2026
…e-cache` and `--only` (#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]>
becker33
pushed a commit
that referenced
this pull request
Jan 11, 2026
…e-cache` and `--only` (#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]> Signed-off-by: Gregory Becker <[email protected]>
becker33
pushed a commit
that referenced
this pull request
Jan 12, 2026
…e-cache` and `--only` (#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]> Signed-off-by: Gregory Becker <[email protected]>
becker33
pushed a commit
that referenced
this pull request
Jan 15, 2026
…e-cache` and `--only` (#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]> Signed-off-by: Gregory Becker <[email protected]>
vjranagit
pushed a commit
to vjranagit/spack
that referenced
this pull request
Jan 18, 2026
…e-cache` and `--only` (spack#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]> Signed-off-by: Gregory Becker <[email protected]>
becker33
pushed a commit
that referenced
this pull request
Jan 22, 2026
…e-cache` and `--only` (#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]> Signed-off-by: Gregory Becker <[email protected]>
becker33
pushed a commit
that referenced
this pull request
Jan 26, 2026
…e-cache` and `--only` (#51593) Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own: `BuildGraph`. * Implement cache related flags: `--use-buildcache (dependencies/package):(always,never,auto)`, `--cache-only`, `--use-cache` * Implement `--only` flag: * `--only dependencies` is implemented by pruning roots just like already installed packages are pruned, and * `--only package` is implemented by raising if after pruning non-roots are in the install queue. Plus add a bunch of tests related to the build graph object, which run in ~0.4s. Signed-off-by: Harmen Stoppels <[email protected]> Signed-off-by: Gregory Becker <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement various flags that influence the build graph the new installer works on. Turn this graph into a class of its own:
BuildGraph.--use-buildcache (dependencies/package):(always,never,auto),--cache-only,--use-cache--onlyflag:--only dependenciesis implemented by pruning roots just like already installed packages are pruned, and--only packageis implemented by raising if after pruning non-roots are in the install queue.Plus add a bunch of tests related to the build graph object, which run in ~0.4s.