A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
Go to file
Hadrien G 14685ae552
Adapt to the latest Acts developments (#16385)
* Adapt to the latest Acts developments

A long time ago, the Acts project (whose name was then capitalized ACTS) used
to maintain multiple software repositories:

- The heart of the tracking toolkit was located in the `acts-core` repository
- Fast simulation extensions were located in the `acts-fatras` repository
- Advanced usage examples were located in the `acts-framework` repository

This multi-repository organization, however, has been a source of constant
pain, which is why the various projects were gradually merged into a single
mono-repo, called `acts`. Today, with the integration of `acts-framework`,
this merging process is reaching completion.

The present pull request adapts the Acts package to this evolution by...

- Renaming the package to `acts`, reflecting the new repository name
- Renaming the `test` variant to `unit_tests`, reflecting current CMake naming
- Adding the new build variants that were inherited from `acts-framework`
- Acknowledging the change of semantics of the `examples` variant, and only
  supporting the new ones (as the former variant was almost unused)
- Liberally using alphabetical order to make the package code more readable
- Recording a large number of conflicts, some of which are introduced by the
  merging of `acts-framework` and some of which already existed before
- Using the new capitalization of "Acts"

* Add acts v0.23

* Update dd4hep version requirement

* Add acts v0.22.1 bugfix
2020-05-07 08:40:31 -05:00
.github macOS Package Builds (nightly) (#16345) 2020-05-06 11:51:29 -07:00
bin spack-python should exec spack python (#15738) 2020-03-29 19:38:15 -07:00
etc/spack/defaults darwin: cut DYLD_LIBRARY_PATH from default modules 2020-04-16 16:17:35 -07:00
lib/spack bugfix: spack shouldn't fail in an incomplete environment (#16473) 2020-05-07 02:30:09 -07:00
share/spack Automatically find externals (#15158) 2020-05-05 17:37:34 -07:00
var/spack Adapt to the latest Acts developments (#16385) 2020-05-07 08:40:31 -05:00
.codecov.yml Use spack commands --format=bash to generate shell completion (#14393) 2020-01-22 21:31:12 -08:00
.coveragerc Use spack commands --format=bash to generate shell completion (#14393) 2020-01-22 21:31:12 -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 Spelling fixes (#15805) 2020-04-01 12:02:26 -05:00
.gitattributes git: add .gitattributes file (#13947) 2019-12-02 01:35:38 -08:00
.gitignore Add vscode files to gitignore (#16270) 2020-04-24 09:31:03 +02: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 travis: extend the list of e-mails being notified of failures (#16352) 2020-04-28 14:55:44 +02:00
CHANGELOG.md Merge branch 'releases/v0.14' into develop 2020-04-15 15:27:00 -07:00
COPYRIGHT tests: finish removing pyqver from the repository (#14294) 2019-12-24 17:37:03 -08:00
LICENSE-APACHE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
LICENSE-MIT copyright: update copyright dates for 2020 (#14328) 2019-12-30 22:36:56 -08:00
NOTICE relicense: update COPYRIGHT, LICENSE-*, README, CONTRIBUTING, and NOTICE 2018-10-17 14:42:06 -07:00
pytest.ini Recover coverage from subprocesses during unit tests (#15354) 2020-03-05 16:54:29 -08:00
README.md macOS Package Builds (nightly) (#16345) 2020-05-06 11:51:29 -07:00

Spack Spack

Build Status Linux Builds macOS Builds (nightly) 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 zlib

Documentation

Full documentation is available, or run spack help or spack help --all.

Tutorial

We maintain a hands-on tutorial. It covers basic to advanced usage, packaging, developer features, and large HPC deployments. You can do all of the exercises on your own laptop using a Docker container.

Feel free to use these materials to teach users at your organization about Spack.

Community

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

Resources:

Contributing

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.

Code of Conduct

Please note that Spack has a Code of Conduct. By participating in the Spack community, you agree to abide by its rules.

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