build-system-archive-import-examples
Overview
Examples for importing precompiled binary tarball and zip archives into various CI/CD build and packaging systems
Redistrib JSON
Sample scripts for parsing redistrib_${label}.json manifests (JSON schema).
- Downloads each archive
- Validates SHA256 checksums
- Extracts archives
- Flattens into a collapsed directory structure
Python Usage
usage: parse_redist.py (-u URL | [-l LABEL] [-p PRODUCT] | --channel CHANNEL) [-o OUTPUT] [--list]
option filters: [--component COMPONENT] ([--os OS] [--arch ARCH])
option toggles: [--no-download] [--no-checksum] [--no-extract] [--no-flatten]
note: for this reference script, Python 3.8 or later is required
Example (python)
python3 ./parse_redist.py --product cuda --label 11.4.2
or equivalent
python3 ./parse_redist.py --url https://developer.download.nvidia.com/compute/cuda/redist/redistrib_11.4.2.json
Repo Channels CDN (packages.nvidia.com)
Use --channel to resolve a release from the NVIDIA Repo Channels CDN
(packages.nvidia.com) instead of
developer.download.nvidia.com. --list shows what a product publishes, and
--channel resolves the release through the channel's releases.json,
verifying the content-addressed (CAS) manifest checksum before parsing it. Omit
--label to take the newest version in the channel:
python3 ./parse_redist.py --list --product cuda
python3 ./parse_redist.py --channel preview --product cuda
python3 ./parse_redist.py --channel archive --product cuda --label 13.4.0
BASH Usage
USAGE: ./shell-parse.sh (--url= | [--product=] [--label=]) [--input=] [--output=]
[--component=] [--os=] [--arch=] [--variant=]
[-W] [-S] [-X] [-F] [--list] [--latest] [--help]
note: for this reference script,
jq,curl,wget, etc. are required
Example (bash)
./shell-parse.sh --product=cuda --label=12.8.0
or equivalent
./shell-parse.sh --product=cuda --latest
CMake
FindCUDAToolkit
See example cmake/1_FindCUDAToolkit/
ExternalProject
See example cmake/2_ExternalProject/
Bazel
pkg_tar
See example bazel/1_pkg_tar/
Contributing
See CONTRIBUTING.md
Metadata
Release files for nvidia-binarchive 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nvidia_binarchive-0.7.0-py3-none-any.whl | Python 3 | none | any | Details for nvidia_binarchive-0.7.0-py3-none-any.whl |
Release files / nvidia_binarchive-0.7.0-py3-none-any.whl
| Download URL | nvidia_binarchive-0.7.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef891f5ca45046e0ecbd19d8dd118d1941eb17d98eb339e7e897a5f1ec05e206
|
|
BLAKE2b-256 checksum How to use checksums |
69d20299c211028e0f4141e6a45e2201a3717ef8ca729bfdbfd3395ceee23eea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logSecurity for nvidia-binarchive 0.7.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for nvidia_binarchive-0.7.0-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.