Binary Archive v3 format and schema - Githubissues

NVIDIA / build-system-archive-import-examples

Examples for importing precompiled binary tarball and zip archives into various build and packaging systems

MIT License

10 stars 5 forks source link

Binary Archive v3 format and schema #4

Closed kmittman closed 1 year ago

kmittman commented 1 year ago

Brainstorming ideas for possible future improvements

ARCHIVE FORMAT

Zstandard compression, i.e. *-archive.tar.zstd
- Smaller tarball size
- Faster compression
- Faster decompression
Special cases for archive split
- NVIDIA driver sub-components
- by CUDA Major version (CUDA Minor version compatibility)

SCHEMA

Array of build dependencies
- Including min/max range
Array of runtime dependencies
- Including min/max range
Array of recent changes
- New or renamed components
- Removed components
- Split components
Link to component LICENSE.txt, perhaps a new key:
- license_url
- :heavy_check_mark: There is already a LICENSE.txt file in each component's directory
- :heavy_check_mark: There is already a LICENSE file in each component tarball/zip archive

RELATED

Detached GPG signature per manifest
git repo of releases
- subscribe to XML/atom feed

Please provide your suggestions, arguments in favor or against any of the above ideas, etc. in a comment.

kmittman commented 1 year ago

Received suggestion to also add top-level key release_label: 1.2.3 matching the filename label.

kmittman commented 1 year ago

Implemented some of these as v3 schema

[x] Special cases for archive split: by CUDA Major version (CUDA Minor version compatibility)
[x] Array of variants
[x] Link to component LICENSE.txt, perhaps a new key: license_url
[x] Added release_label and release_product keys

Closing this and opening a new issue for v4 proposed changes