hlrs-software-stack/spack
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Clone of the official spack repository with modifications for HLRS HAWK
1108 commits 3 branches 52 tags 188 MiB
Python 97%
Shell 2.1%
Prolog 0.4%
C 0.2%
Find a file
Peter Scheibel 099fa1df34 Use nose to run unit tests. 
1. Adding a plugin to keep track of the total number of tests run as well as the
number of tests with failures/errors.
2. Some nose plugins (including xunit which will be added in a future commit)
assign stdout to a stream object that does not have a .fileno attribute.
spack.util.executable.Executable now avoids passing stdout to subprocess (and
always uses subprocess.PIPE)

TODO:
1. Still need to figure out how to activate the plugin (as of now it is
being ignored by nose). Newer versions of nose appear to make this simpler
(e.g. the "addplugins" argument to nose.run)
2. Need to include new version of nose in order to use xunit
2015-11-23 18:59:48 -08:00
bin Add a fix/warning so that stale .pyc files don't kill Spack. 2015-11-23 17:49:39 -08:00
lib/spack Use nose to run unit tests. 2015-11-23 18:59:48 -08:00
share/spack Added missing $_sp_flags to spack.csh so options -d -k -m -p -v get passed on to spack proper. 2015-11-06 10:53:22 -08:00
var/spack cleaning up commits for merge request 2015-11-23 16:16:52 -08:00
.gitignore YAML config files for compilers and mirrors 2015-05-18 16:01:21 -07:00
.mailmap Add .mailmap file 2015-08-13 00:18:19 -07:00
LICENSE Callpath build works when a tag is fetched from git. 2014-10-03 16:55:53 -07:00
README.md Add Spack logo. 2015-10-18 19:14:40 -07:00

README.md

image

Spack is a package management tool designed to support multiple versions and configurations of software on a wide variety of platforms and environments. It was designed for large supercomputing centers, where many users and application teams share common installations of software on clusters with exotic architectures, using libraries that do not have a standard ABI. Spack is non-destructive: installing a new version does not break existing installations, so many 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 written in pure Python, and specs allow package authors to write a single build script for many different builds of the same package.

See the Feature Overview for examples and highlights.

To install spack and install your first package:

$ git clone https://github.com/scalability-llnl/spack.git
$ cd spack/bin
$ ./spack install libelf

Documentation

Full documentation for Spack is also available.

Get Involved!

Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, or even new core features.

Mailing list

If you are interested in contributing to spack, the first step is to join the mailing list. We're using a Google Group for this, and you can join it here:

Contributions

At the moment, contributing to Spack is relatively simple. Just send us a pull request. When you send your request, make develop the destination branch.

Spack is using a rough approximation of the Git Flow branching model. The develop branch contains the latest contributions, and master is always tagged and points to the latest stable release.

Authors

Many thanks go to Spack's contributors.

Spack was originally written by Todd Gamblin, tgamblin@llnl.gov.

Release

Spack is released under an LGPL license. For more details see the LICENSE file.

LLNL-CODE-647188