0b606b01dc
1. support version 3.1.3, which now depends on sundials@6
2. support version 3.1.2:, which broke the two patch files and
therefore the two patch files have been replaced by more flexible
filter_file() commands inside a patch() function.
3. rename the variant for python extension from using the package name
"+pyuqtk" to the more standard "+python"
4. add maintainers @omsai and the upstream developer @bjdebus who
offered to help with the spack packaging.
5. swig should only be a build-time dependency. swig is only
necessary until @:3.1.0
6. confirmed python dependencies are correct by inspecting imports,
subset python dependencies type to build, run, and confirmed all
31 build-time tests pass including the 9 python tests:
```console
$ spack env create uqtk-dev
$ spack add uqtk@3.1.3
$ spack install --test root && cat $(spack location -i uqtk)/.spack/install-time-test-log.txt
==> Testing package uqtk-3.1.3-nok6fut
==> [2023-04-19-14:56:25.005361] Running build-time tests
==> [2023-04-19-14:56:25.005536] RUN-TESTS: build-time tests [check]
==> [2023-04-19-14:56:25.009543] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' '-n' 'test'
==> [2023-04-19-14:56:25.014903] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' 'test'
Running tests...
/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/cmake-3.26.3-zjmsfz23j5l4ytniz26uzvxonlu5qebr/bin/ctest --force-new-ctest-process
Test project /tmp/omsai/spack-stage/spack-stage-uqtk-3.1.3-nok6fut47h42cnaau7wkoohgqy5f2qqa/spack-build-nok6fut
Start 1: ArrayReadAndWrite
Start 2: ArrayDelColumn
Start 3: Array1DMiscTest
Start 4: Array2DMiscTest
1/31 Test #1: ArrayReadAndWrite ................ Passed 0.01 sec
Start 5: ArraySortTest
2/31 Test #2: ArrayDelColumn ................... Passed 0.01 sec
Start 6: MultiIndexTest
3/31 Test #3: Array1DMiscTest .................. Passed 0.01 sec
Start 7: CorrTest
4/31 Test #4: Array2DMiscTest .................. Passed 0.01 sec
Start 8: QuadLUTest
5/31 Test #5: ArraySortTest .................... Passed 0.02 sec
Start 9: MCMC2dTest
6/31 Test #6: MultiIndexTest ................... Passed 0.01 sec
Start 10: MCMCRandomTest
7/31 Test #8: QuadLUTest ....................... Passed 0.02 sec
Start 11: MCMCNestedTest
8/31 Test #10: MCMCRandomTest ................... Passed 0.02 sec
Start 12: Deriv1dTest
9/31 Test #12: Deriv1dTest ...................... Passed 0.01 sec
Start 13: SecondDeriv1dTest
10/31 Test #13: SecondDeriv1dTest ................ Passed 0.01 sec
Start 14: GradHessianTest
11/31 Test #11: MCMCNestedTest ................... Passed 0.03 sec
Start 15: GradientPCETest
12/31 Test #14: GradHessianTest .................. Passed 0.01 sec
Start 16: PCE1dTest
13/31 Test #15: GradientPCETest .................. Passed 0.01 sec
Start 17: PCEImplTest
14/31 Test #16: PCE1dTest ........................ Passed 0.01 sec
Start 18: PCELogTest
15/31 Test #18: PCELogTest ....................... Passed 0.01 sec
Start 19: Hessian2dTest
16/31 Test #19: Hessian2dTest .................... Passed 0.01 sec
Start 20: BCS1dTest
17/31 Test #20: BCS1dTest ........................ Passed 0.01 sec
Start 21: BCS2dTest
18/31 Test #21: BCS2dTest ........................ Passed 0.01 sec
Start 22: LowRankRegrTest
19/31 Test #22: LowRankRegrTest .................. Passed 0.01 sec
Start 23: PyModTest
20/31 Test #17: PCEImplTest ...................... Passed 0.07 sec
Start 24: PyArrayTest
21/31 Test #23: PyModTest ........................ Passed 0.08 sec
Start 25: PyArrayTest2
22/31 Test #25: PyArrayTest2 ..................... Passed 0.30 sec
Start 26: PyQuadTest
23/31 Test #24: PyArrayTest ...................... Passed 1.44 sec
Start 27: PyBCSTest1D
24/31 Test #26: PyQuadTest ....................... Passed 1.68 sec
Start 28: PyBCSTest2D
25/31 Test #27: PyBCSTest1D ...................... Passed 1.66 sec
Start 29: PyBADPTest
26/31 Test #7: CorrTest ......................... Passed 3.43 sec
Start 30: PyRegressionTest
27/31 Test #28: PyBCSTest2D ...................... Passed 1.50 sec
Start 31: PyGalerkinTest
28/31 Test #9: MCMC2dTest ....................... Passed 3.90 sec
29/31 Test #29: PyBADPTest ....................... Passed 1.66 sec
30/31 Test #30: PyRegressionTest ................. Passed 1.72 sec
31/31 Test #31: PyGalerkinTest ................... Passed 1.63 sec
100% tests passed, 0 tests failed out of 31
Total Test time (real) = 5.35 sec
==> [2023-04-19-14:56:30.382797] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' '-n' 'check'
==> [2023-04-19-14:56:30.385983] Target 'check' not found in Makefile
```
|
||
|---|---|---|
| .github | ||
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| var/spack | ||
| .codecov.yml | ||
| .dockerignore | ||
| .flake8 | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .readthedocs.yml | ||
| CHANGELOG.md | ||
| CITATION.cff | ||
| COPYRIGHT | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| NOTICE | ||
| pyproject.toml | ||
| pytest.ini | ||
| README.md | ||
| SECURITY.md | ||
Spack
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 -c feature.manyFiles=true 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.
For a cheat sheet on Spack syntax, run spack help --spec.
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:
- Slack workspace: spackpm.slack.com. To get an invitation, visit slack.spack.io.
- Github Discussions: not just for discussions, also Q&A.
- Mailing list: groups.google.com/d/forum/spack
- Twitter: @spackpm. Be sure to
@mentionus!
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 our CI process. To run these tests locally, and for helpful tips on git, see our Contribution Guide.
Spack's develop branch has the latest contributions. Pull requests
should target develop, and users who want the latest package versions,
features, etc. can use develop.
Releases
For multi-user site deployments or other use cases that need very stable software installations, we recommend using Spack's stable releases.
Each Spack release series also has a corresponding branch, e.g.
releases/v0.14 has 0.14.x versions of Spack, and releases/v0.13 has
0.13.x versions. We backport important bug fixes to these branches but
we do not advance the package versions or make other changes that would
change the way Spack concretizes dependencies within a release branch.
So, you can base your Spack deployment on a release branch and git pull
to get fixes, without the package churn that comes with develop.
The latest release is always available with the releases/latest tag.
See the docs on releases for more details.
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:
- Todd Gamblin, Matthew P. LeGendre, Michael R. Collette, Gregory L. Lee, Adam Moody, Bronis R. de Supinski, and W. Scott Futral. The Spack Package Manager: Bringing Order to HPC Software Chaos. In Supercomputing 2015 (SC’15), Austin, Texas, November 15-20 2015. LLNL-CONF-669890.
On GitHub, you can copy this citation in APA or BibTeX format via the "Cite this repository"
button. Or, see the comments in CITATION.cff for the raw BibTeX.
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-811652