Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Spack
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
eic_tools
Spack
Commits
3060f279
Commit
3060f279
authored
9 years ago
by
becker33
Browse files
Options
Downloads
Plain Diff
Merge pull request #536 from adamjstewart/fixes/doc_typos
Documentation typo fixes
parents
1c7f754e
bae03404
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
lib/spack/docs/index.rst
+1
-1
1 addition, 1 deletion
lib/spack/docs/index.rst
lib/spack/docs/packaging_guide.rst
+6
-6
6 additions, 6 deletions
lib/spack/docs/packaging_guide.rst
with
7 additions
and
7 deletions
lib/spack/docs/index.rst
+
1
−
1
View file @
3060f279
...
...
@@ -18,7 +18,7 @@ configurations can coexist on the same system.
Most importantly, Spack is *simple*. It offers a simple *spec* syntax
so that users can specify versions and configuration options
concisely. Spack is also simple for package authors: package files
are writt
i
n in pure Python, and specs allow package authors to
are writt
e
n in pure Python, and specs allow package authors to
maintain a single file for many different builds of the same package.
See the :doc:`features` for examples and highlights.
...
...
This diff is collapsed.
Click to expand it.
lib/spack/docs/packaging_guide.rst
+
6
−
6
View file @
3060f279
...
...
@@ -419,7 +419,7 @@ directory to the directory containing the downloaded archive before it
calls your ``install`` method. Within ``install``, the path to the
downloaded archive is available as ``self.stage.archive_file``.
Here is an example snippet for packages distribu
e
td as self-extracting
Here is an example snippet for packages distribut
e
d as self-extracting
archives. The example sets permissions on the downloaded file to make
it executable, then runs it with some arguments.
...
...
@@ -1556,12 +1556,12 @@ you ask for a particular spec.
``Concretization Policies``
~~~~~~~~~~~~~~~~~~~~~~~~~~~
A user may have certain p
e
rfer
r
ences for how packages should
A user may have certain pr
e
ferences for how packages should
be concretized on their system. For example, one user may prefer packages
built with OpenMPI and the Intel compiler. Another user may prefer
packages be built with MVAPICH and GCC.
Spack can be configur
at
ed to prefer certain compilers, package
Spack can be configured to prefer certain compilers, package
versions, depends_on, and variants during concretization.
The preferred configuration can be controlled via the
``~/.spack/packages.yaml`` file for user configuations, or the
...
...
@@ -1588,16 +1588,16 @@ At a high level, this example is specifying how packages should be
concretized. The dyninst package should prefer using gcc 4.9 and
be built with debug options. The gperftools package should prefer version
2.2 over 2.4. Every package on the system should prefer mvapich for
its MPI and gcc 4.4.7 (except for Dyninst, which overrides this by p
e
rfering gcc 4.9).
its MPI and gcc 4.4.7 (except for Dyninst, which overrides this by pr
e
fer
r
ing gcc 4.9).
These options are used to fill in implicit defaults. Any of them can be overwritten
on the command line if explicitly requested.
Each packages.yaml file begin with the string ``packages:`` and
Each packages.yaml file begin
s
with the string ``packages:`` and
package names are specified on the next level. The special string ``all``
applies settings to each package. Underneath each package name is
one or more components: ``compiler``, ``variants``, ``version``,
or ``providers``. Each component has an ordered list of spec
``constraints``, with earlier entries in the list being prefered over
``constraints``, with earlier entries in the list being prefer
r
ed over
later entries.
Sometimes a package installation may have constraints that forbid
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
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