Clone of the official spack repository with modifications for HLRS HAWK
Find a file
Todd Gamblin a750237532
flake8: add exceptions for overly pedantic camelcase rules from pep8-naming (#11477)
Rules N813 and N814 prevented import statements like this:

  xml.etree.ElementTree as et
  xml.etree.ElementTree as ET

But both of those seem pretty reasonable.  We see no reason to require any camelcase import to be imported "as" a camelcase word.
2019-05-16 09:47:02 +02:00
.github/ISSUE_TEMPLATE bug report template: suggest --stacktrace instead of -s (#10548) 2019-02-07 21:06:57 -06:00
bin release workflow: Add build scripts for jobs and means to upload pkgs 2019-02-21 15:37:35 -06:00
etc/spack/defaults ninja: drop python as a run dep (#11347) 2019-05-07 13:07:24 -04:00
lib/spack fix suite-sparse built with tbb from intel-parallel-studio (#11134) 2019-05-15 11:03:19 -07:00
share/spack bugfix: Do not run spack spec in the test environment for Python 2.6 2019-05-10 13:13:44 -07:00
var/spack Update flecsi package.py (#11442) 2019-05-15 15:29:08 -06:00
.codecov.yml coverage: use kcov to get coverage for our cc script 2018-12-29 23:47:29 -08:00
.coveragerc coverage: use kcov to get coverage for our cc script 2018-12-29 23:47:29 -08:00
.dockerignore fix multiple issues with the docker images (#9718) 2018-12-20 11:11:55 -08:00
.flake8 flake8: add exceptions for overly pedantic camelcase rules from pep8-naming (#11477) 2019-05-16 09:47:02 +02:00
.flake8_packages flake8: add exceptions for overly pedantic camelcase rules from pep8-naming (#11477) 2019-05-16 09:47:02 +02:00
.gitignore env: add spack env command, along with env.yaml schema and tests 2018-11-09 00:31:24 -08:00
.mailmap Update for 'eccodes'. (#6604) 2017-12-08 09:34:37 +01:00
.readthedocs.yml Updated Sphinx configuration (#11165) 2019-04-11 14:38:52 -07:00
.travis.yml tests: stop testing Python 3.4 2019-05-11 16:39:53 -07:00
CODE_OF_CONDUCT.md Make CODE_OF_CONDUCT.md more Spack-specific (#11403) 2019-05-08 17:49:03 -07:00
CONTRIBUTING.md relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
COPYRIGHT relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
LICENSE-APACHE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
LICENSE-MIT copyright: update license headers for 2013-2019 copyright. 2019-01-01 00:44:28 -08:00
NOTICE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
README.md README: LLNL release number and SPDX id don't need to be monospaced. 2019-01-01 00:44:28 -08:00

Spack Spack

Build Status codecov Read the Docs Slack

Spack is a multi-platform package manager that builds and installs multiple versions and configurations of software. It works on Linux, macOS, and many supercomputers. Spack is non-destructive: installing a new version of a package does not break existing installations, so many configurations of the same package can coexist.

Spack offers a simple "spec" syntax that allows users to specify versions and configuration options. Package files are written in pure Python, and specs allow package authors to write a single script for many different builds of the same package. With Spack, you can build your software all the ways you want to.

See the Feature Overview for examples and highlights.

To install spack and your first package, make sure you have Python. Then:

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

Documentation

Full documentation for Spack is the first place to look.

Try the Spack Tutorial, to learn how to use spack, write packages, or deploy packages for users at your site.

See also:

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, join the mailing list. We're using Google Groups for this:

Slack channel

Spack has a Slack channel where you can chat about all things Spack:

Sign up here to get an invitation mailed to you.

Twitter

You can follow @spackpm on Twitter for updates. Also, feel free to @mention us in in questions or comments about your own experience with Spack.

Contributions

Contributing to Spack is relatively easy. Just send us a pull request. When you send your request, make develop the destination branch on the Spack repository.

Your PR must pass Spack's unit tests and documentation tests, and must be PEP 8 compliant. We enforce these guidelines with Travis CI. To run these tests locally, and for helpful tips on git, see our Contribution Guide.

Spack uses 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 created by Todd Gamblin, tgamblin@llnl.gov.

Citing Spack

If you are referencing Spack in a publication, please cite the following paper:

License

Spack is distributed under the terms of both the MIT license and the Apache License (Version 2.0). Users may choose either license, at their option.

All new contributions must be made under both the MIT and Apache-2.0 licenses.

See LICENSE-MIT, LICENSE-APACHE, COPYRIGHT, and NOTICE for details.

SPDX-License-Identifier: (Apache-2.0 OR MIT)

LLNL-CODE-647188