![]() * py-tensorflow: add versions 2.5.0 and 2.6.0 - add version 2.5.0 - add version 2.6.0 - add patches for newer protobuf - set constraints * Remove import os. left over from testing * Remove unused patch file * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Add py-clang dependency * Adjust py-clang constraint * Build tensorflow with tensorboard - tensorflow - added 2.6.1 and 2.6.2 versions - tensorboard - have bazel use number of jobs set by spack - add versions and constraints - new package: py-tensorboard-data-server - use wheel for py-tensorboard-plugin-wit This package can not build with newer versions of bazel that are needed for newer versions of py-tensorboard. * Update var/spack/repos/builtin/packages/py-clang/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Remove empty line at end of file * Fix import sorting * Adjust python dependencies on py-clang * Add version 2.7.0 of pt-tensorflow and py-tensorboard * Adjust bazel constraints * bazel-4 support begins with py-tensorflow-2.7.0 * Adjust dependencies * Loosen cuda constraint on versions > 2.5 Tensorflow-2.5 and above can use cuda up to version 11.4. * Add constraints to patch The 0008-Fix-protobuf-errors-when-using-system-protobuf.patch patch should only apply to versions 2.5 and above. * Adjust constraints - versions 2.4 and below need protobuf-3.12 and below - versions 2.4 and above can use up to cuda-11.4 - versions 2.2 and below can not use cudnn-8 - the null_linker_bin patch should only be applied to versions 2.5 and above. * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/py-tensorflow/package.py Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Fix py-grpcio dependency for version 2.7 Also, make sure py-h5py mpi specs are consistent. * Add llvm as run dependency. * Fix python spec for py-tensorboard * Fix py-google-auth spec for py-tensorboard * Do not override the pip spec for tensorboard-plugin-wit * Converted py-tensorboard-plugin-wit to wheel only package * Fix bazel dependency spec in tensorflow * Adjust pip masks - allow tensorboard to be specified in pip constraints - mask tensorflow-estimator * Remove blank line at end of file * Adjust pip constraints in setup.py Also, adjust constraint on a patch that is fixed in 2.7 * Fix flake8 error Adjust formatting for consistency. * Get bazel dep right * Fix old cudnn dependency, caught in audit test * Adjust the regex to ensure proper line is changed * Add py-libclang package - Stripped the py-clang package down to just version 5 - added comments to indicate the purpose of py-clang and that py-libclang should be preferred - set dependencies accordingly in py-tensorflow * Remove cap on py-h5py dependency for v2.7 * Add TODO entries for tensorflow-io-gcs-filesystem * Edit some comments * Add phases and select python in PATH for tensorboard-data-server * py-libclang - remove py-wheel dependency - remove raw string notation in filter_file * py-tensorboard-data-server - remove py-wheel dep - remove py-pip dep - use python from package class * py-tensorboard-plugin-wit - switch to PythonPackage - add version 1.8.1 - remove unneeded code * Add comment as to why a wheel is need for tensorboard-plugin-wit * remove which pip from tensorboard-data-server * Fix dependency specs in tensorboard * tweak dependencies for tensorflow * fix python constraint * Use llvm libs property * py-tensorboard-data-server - merge build into install - use std_pip_args * remove py-clang dependency * remove my edits to py-tensorboard-plugin-wit Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> |
||
---|---|---|
.github | ||
bin | ||
etc/spack/defaults | ||
lib/spack | ||
share/spack | ||
var/spack | ||
.codecov.yml | ||
.dockerignore | ||
.flake8 | ||
.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.
- Mailing list: groups.google.com/d/forum/spack
- Twitter: @spackpm. Be sure to
@mention
us!
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