spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.

Age	Commit message (Collapse)	Author	Files	Lines
2017-11-06	add artisanal handcrafted SVG Spack logo. (#6165)	Todd Gamblin	1	-1/+1
	- 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.
2017-11-06	Fix spack view hardlink (#6130)	Johann Klähn	2	-1/+14
	Fix a typo in "spack view hardlink" introduced in #5415 ("os.hardlink" does not exist).
2017-11-06	Introduce static_to_shared_library function (#6092)	Michael Kuhn	2	-0/+197
	The static_to_shared_library function takes an existing static library and produces a shared library based on it.
2017-11-06	Docs: MPI as Root (#6156)	Axel Huebl	1	-0/+3
	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
2017-11-06	Add back help placeholder for "spack load" (#6127)	scheibelp	5	-8/+30
	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.
2017-11-04	Replace github.com/llnl/spack with github.com/spack/spack (#6142)	Todd Gamblin	277	-298/+298
	We moved to a new GitHub org! Now make the code and docs reflect that.
2017-11-03	Fix restaging of resources (#5681)	Johann Klähn	1	-12/+22
	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.
2017-11-03	spack fetch: don't fetch externals. (#6124)	Todd Gamblin	1	-1/+8
	Fixes #6123 spack fetch shouldn't attempt to fetch external deps when invoked with --dependencies.
2017-11-02	Configure user for mock Git repository (#6128)	Michael Kuhn	1	-0/+2
	If user.useConfigOnly is set globally and no name or e-mail is configured, the git_fetch tests fail.
2017-11-02	test_activations: also test perl activations	Ben Boeckel	1	-0/+103

2017-11-02	test_activations: test Python's extension logic	Peter Scheibel	1	-0/+168

2017-11-02	spec: support a test prefix	Peter Scheibel	1	-0/+5
	This is used in tests to test real packages without actually building and installing them.
2017-11-02	view: test conflicting packages in views	Ben Boeckel	1	-0/+25

2017-11-02	view: test that extension paths exist	Ben Boeckel	1	-0/+23

2017-11-02	filesystem_view: reject packages with activations	Ben Boeckel	3	-11/+26
	If there are extensions that are globally activated, reject adding them to a view. Those extensions should not be implicitly activated.
2017-11-02	view: test viewing external packages	Ben Boeckel	1	-0/+9

2017-11-02	view: add a test for extension activation	Ben Boeckel	1	-0/+82

2017-11-02	extensions: support only showing a subset of information	Ben Boeckel	1	-32/+60

2017-11-02	extensions: support acting on a view	Ben Boeckel	3	-12/+40
	This allows extensions to be (de)activated and queried within a view rather than only acting on the global installation.
2017-11-02	view: use the FilesystemView abstraction for creating views	Oliver Breitwieser	1	-198/+127

2017-11-02	view: fix some docstrings for arguments	Oliver Breitwieser	1	-2/+2

2017-11-02	filesystem_view: do not link external packages	Ben Boeckel	1	-0/+10

2017-11-02	filesystem_view: add a class to handle a view via a Yaml description	Oliver Breitwieser	1	-0/+524

2017-11-02	package: support removing dependencies when deactivating	Oliver Breitwieser	1	-6/+14

2017-11-02	conftest: mock out spack.store.extensions as well	Ben Boeckel	1	-0/+4

2017-11-02	views: support querying view layouts as well	Oliver Breitwieser	5	-26/+56
	This abstracts out the layout in use between the global installations and a specific view.
2017-11-02	link_tree: support choosing the link function	Oliver Breitwieser	1	-2/+2
	This can be used to make hardlinks rather than symlinks.
2017-11-02	link_tree: support ignoring conflicts	Oliver Breitwieser	1	-3/+16

2017-11-02	directory_layout: add a YamlExtensionsLayout class	Oliver Breitwieser	1	-0/+25
	This uses a view to query extensions.
2017-11-02	link_tree: only remove matching files when unmerging	Oliver Breitwieser	1	-1/+6

2017-11-02	directory_layout: factor out an ExtensionsLayout class	Oliver Breitwieser	1	-92/+118

2017-11-02	extensions: add an installed_extensions_for method	Ben Boeckel	2	-1/+11

2017-11-02	database: rename `installed_extensions_for`	Oliver Breitwieser	3	-3/+3
	Views support activating packages, so rename the method because it will soon query what is activated versus what is installed.
2017-11-02	package: support verbosity when activating	Oliver Breitwieser	1	-8/+14

2017-11-02	package: rename `activated` to `is_activated`	Oliver Breitwieser	4	-10/+10
	This allows the activation code to be later given parameters.
2017-11-02	cmd/test: fix a typo in a comment	Ben Boeckel	1	-1/+1

2017-11-02	spec_yaml: fix a typo	Ben Boeckel	1	-1/+1

2017-11-02	view: fix a typo	Oliver Breitwieser	1	-1/+1

2017-11-02	determine full compiler version for gcc-7	Ben Boeckel	1	-1/+4
	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'
2017-11-02	Only use XCode clang wrappers for packages that set use_xcode=True (#6077)	Todd Gamblin	3	-23/+11

2017-11-01	update filename used for cc wrapper invocation debug log (#5837)	scheibelp	3	-3/+8
	The name of the debug log written by the cc compiler wrapper was given by Spec.short_spec, which includes the architecture. Somewhere along the line Spec.format started adding spaces around the architecture property so the filename started including spaces; the cc wrapper script appears to ignore this, so files like spack-cc-bzip2-....in.log (which record the wrapped compiler invocations) were not being generated. This uses a different format string from the spec to generate the wrapper log file names (which does not include spaces).
2017-11-01	Fix user specs which include already-installed packages (#5939)	scheibelp	2	-1/+7
	* when a user-provided spec refers to an already-installed package, packages with patches applied were causing validation errors based on the recorded variants in the package's class * avoid checks on all reserved variants (not just 'patches')
2017-10-30	Auto install available pre-built packages from binary cache (#5242)	scheibelp	5	-30/+62
	* basic functionality to install spec from a binary cache when it's available; this spiders each cache for each package and could likely be more efficient by caching the results of the first check * add spec to db after installing from binary cache * cache (in memory) spec listings retrieved from binary caches * print a warning vs. failing when no mirrors are configured to retrieve pre-built Spack packages * make automatic retrieval of pre-built spack packages from mirrors optional * no code was using the links stored in the dictionary returned by get_specs, so this simplifies the logic to return only a set of specs * print package prefix after installing from binary cache * provide more information to user on install progress
2017-10-27	Bugfix: from_list_url(). (#5780)	Sergey Kosukhin	2	-1/+16
	This fixes a bug in from_list_url where it was referring to a method which no longer exists. This also adds a test for the from_list_url function.
2017-10-26	Package.extends: update semantics when package isn't concrete (#5600)	Ben Boeckel	1	-1/+10
	This updates the logic for Package.extends so that if the spec associated with the package is not concrete, it will report true if the package could extend the given spec; generally speaking a package could extend a spec as long as none of the details associated with its extendee spec conflict with the given spec. When the spec associated with the package is concrete, this function will only report whether the package does extend the given spec. When both the specs are concrete, the semantics are the same as before.
2017-10-26	Buildcache: symlinks, externals, & install-checking (#5894)	Patrick Gartung	4	-61/+62
	* When creating a tar of a package for a build cache, symlinks are preserved (the corresponding path in the newly-created tarfile will be a symlink rather than a copy of the file) * Dont add external packages to a build cache * When installing from binary cache, don't create install prefix until verification is complete
2017-10-26	Colorize "Installing pkg_name" (#5950)	Ondřej Čertík	1	-1/+2
	Now one can quickly visually see in the terminal which packages are installed and where each package begins and ends in the log.
2017-10-25	Check for namespace-qualified packages in repo_for_pkg (#5787)	scheibelp	2	-10/+88
	* Fixes #5754 Previously when RepoPath.repo_for_pkg was invoked with a string, it did not check if the string included a namespace. Any namespace-qualified package provided as a string would not be found (at which point the behavior was to return the highest-precedence repository). * handle nested namespaces for packages specified as strings in repo_for_pkg * add preliminary repository tests * add test which replicates #5754 * refactor repo tests with fixtures * define repo_path equivalent at test-level scope for repo tests * add tests for unknown namespace/package * rename fixture function (no longer prefixed with 'test_')
2017-10-25	Specify base branch for flake8 comparison (#5796)	George Hartzell	1	-1/+6
	Internally we work against a branch named 'llnl/develop', which mirrors the public repository's `develop` branch. It's useful to be able to run flake8 on our changes, using `llnl/develop` as the base branch instead of `develop`. Internally the flake8 subcommand generates the list of changes files using a hardcoded range of `develop...`. This makes the base of that range a command line option, with a default of `develop`. That lets us do this: ``` spack flake8 --base llnl/develop ``` which uses a range of `llnl/develop...`.
2017-10-24	'spack install' can overwrite an existing installation (#5384)	Massimiliano Culpo	4	-52/+274
	'spack install' can now reinstall a spec even if it has dependents, via the --overwrite option. This option moves the current installation in a temporary directory. If the reinstallation is successful the temporary is removed, otherwise a rollback is performed.