Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
spack
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
EBRAINS RI
Tech Hub
Platform
EBRAINS Software Distribution
spack
Commits
734ada1f
Commit
734ada1f
authored
7 months ago
by
Wouter Deconinck
Committed by
Harmen Stoppels
5 months ago
Browse files
Options
Downloads
Patches
Plain Diff
doc: ensure getting_started has bootstrap list output in correct place (#48281)
parent
71712465
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
lib/spack/docs/getting_started.rst
+10
-8
10 additions, 8 deletions
lib/spack/docs/getting_started.rst
with
10 additions
and
8 deletions
lib/spack/docs/getting_started.rst
+
10
−
8
View file @
734ada1f
...
@@ -148,20 +148,22 @@ The first time you concretize a spec, Spack will bootstrap automatically:
...
@@ -148,20 +148,22 @@ The first time you concretize a spec, Spack will bootstrap automatically:
--------------------------------
--------------------------------
zlib@1.2.13%gcc@9.4.0+optimize+pic+shared build_system=makefile arch=linux-ubuntu20.04-icelake
zlib@1.2.13%gcc@9.4.0+optimize+pic+shared build_system=makefile arch=linux-ubuntu20.04-icelake
The default bootstrap behavior is to use pre-built binaries. You can verify the
active bootstrap repositories with:
.. command-output:: spack bootstrap list
If for security concerns you cannot bootstrap ``clingo`` from pre-built
If for security concerns you cannot bootstrap ``clingo`` from pre-built
binaries, you have to disable fetching the binaries we generated with Github Actions.
binaries, you have to disable fetching the binaries we generated with Github Actions.
.. code-block:: console
.. code-block:: console
$ spack bootstrap disable github-actions-v0.4
$ spack bootstrap disable github-actions-v0.6
==> "github-actions-v0.4" is now disabled and will not be used for bootstrapping
==> "github-actions-v0.6" is now disabled and will not be used for bootstrapping
$ spack bootstrap disable github-actions-v0.3
$ spack bootstrap disable github-actions-v0.5
==> "github-actions-v0.3" is now disabled and will not be used for bootstrapping
==> "github-actions-v0.5" is now disabled and will not be used for bootstrapping
You can verify that the new settings are effective with:
.. command-output:: spack bootstrap list
You can verify that the new settings are effective with ``spack bootstrap list``.
.. note::
.. note::
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment