Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
* Allow types and 'any' in variant definitions.
- Previously variant values had to be a tuple or a callable predicate.
- This allows 'any' as shorthand for `lambda x: True` and type objects
as shorthand for "any value of this type".
- Makes variant definitions more readable, keeps lambdas out of
packages for common cases.
* Update packaging tutorial
* Fix bad file reference in packaging tutorial
|
|
|
|
* First draft of the advanced packaging tutorial
* advanced packaging tutorial: improved phrasing
Thanks Denis and Hartzell!
* Fixed typos + reworded a couple of sentences
|
|
* Reworked module file tutorial section
First draft for the SC17 update. This includes:
- adding an introduction on module files + Spack's module
generation blueprints
- adding a set-up section and provide a docker image for easy set-up
- updating all the relevant snippets
- extending a bit some of the concepts that were already touched
* Added reference to #5582 + committed Dockerfiles
Also fixed a couple of typos spotted by Denis.
* module file tutorial: added section on template customization
* module file tutorial: fixed minor typos + rephrased a sentence
* module file tutorial: made explicit that Docker image comes with software
* module file tutorial: improved phrasing and layout.
Thanks Hartzell!
* module file tutorial: added vim and nano to editors
* module file tutorial: fixed typo
* Fixed typos
Thanks Adam!
* module file tutorial: updated Dockerfile + minor changes in introduction
|
|
|
|
Fixes #6154
For compiler options which set values using the syntax "-flag value"
(with a space between the flag and the flag's value) the flag and
value were treated as separate and reordered. This updates Spack's
logic to treat the flag and value as a single unit, even if there is
a space between them. It assumes that all flags are prefixed with
"-" and that all flag values are not.
|
|
* deal with case where symbolic links are copied
* Suggested changes
|
|
* Skip rewriting files that are links (this also avoids issues with parsing
the output of the 'file' command for symlinks)
* Fail rather than warn for several gpg signing issues (e.g. if there is no
key available to sign with)
* Installation with 'buildcache install' only retrieves link and run
dependencies (this matches 'buildcache create' which only creates tarballs
of link/run dependencies)
* Don't rewrite RPATHs for a binary if the binary cached package was created
with relative RPATHs
* Refactor relocate_binary to operate on multiple binaries (given as a
collection of paths). This was likewise done for relocate_text and
make_binary_relative
|
|
- This isn't one of those autogenerated SVGs from a drawing program!
- This is a completely re-traced, minimalist SVG file with clearly
delineated pieces so that your favorite renderer can draw a Spack logo
at whatever resolution you want.
- Included versions with text, as well.
|
|
Fix a typo in "spack view hardlink" introduced in #5415
("os.hardlink" does not exist).
|
|
The static_to_shared_library function takes an existing static library
and produces a shared library based on it.
|
|
New versions of OpenMPI need `--allow-run-as-root` for
running as root:
http://www.open-mpi.de/doc/v2.0/man1/mpirun.1.php#toc22
|
|
Fixes #6126
#3183 removed the print_help function from the "modules" module.
This adds it back so that if a user invokes 'spack load foo' without
having sourced an environment setup script, they will be prompted
to do so. This also improves the placeholder message to tell the
user to invoke 'spack' as shell function rather than as an executable.
|
|
We moved to a new GitHub org! Now make the code and docs reflect that.
|
|
Part of the resource staging process is to place downloaded/expanded
files in the root stage. This was not happening when a resource stage
was restaged.
|
|
Fixes #6123
spack fetch shouldn't attempt to fetch external deps when invoked
with --dependencies.
|
|
If user.useConfigOnly is set globally and no name or e-mail is
configured, the git_fetch tests fail.
|
|
|
|
|
|
This is used in tests to test real packages without actually building
and installing them.
|
|
|
|
|
|
If there are extensions that are globally activated, reject adding them
to a view. Those extensions should not be implicitly activated.
|
|
|
|
|
|
|
|
This allows extensions to be (de)activated and queried within a view
rather than only acting on the global installation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This abstracts out the layout in use between the global installations
and a specific view.
|
|
This can be used to make hardlinks rather than symlinks.
|
|
|
|
This uses a view to query extensions.
|
|
|
|
|
|
|
|
Views support activating packages, so rename the method because it will
soon query what is activated versus what is installed.
|
|
|
|
This allows the activation code to be later given parameters.
|
|
|
|
|
|
|
|
Fixes #5778.
Spack uses 'gcc -dumpversion' to determine the full version of gcc.
'gcc -dumpversion' no longer gives the full version on gcc 7.2.0.
'gcc -dumpfullversion' is required instead. This PR detects when
'gcc -dumpversion' gives a truncated version of '7' and in that
case retrieves the full version with 'gcc -dumpfullversion'
|
|
|