Repository navigation
Document build_env metadata and reproducible tarballs - #87
Merged
Merged
Conversation
Add the optional build_env metadata field: the names and versions of the tools that created the package tarball. Hex records its version there with hexpm/hex#1252, so the version needed to rebuild a package and compare checksums can be read from the package alone. Add recommendations to the package tarball spec for creating tarballs whose bytes only depend on the files and the tool versions: entry order, timestamps, owners, modes, NFC names, the gzip header and the order of metadata keys. They describe what hex_core does since hexpm/hex_core#228. They aren't requirements, and different tools aren't expected to produce the same bytes as each other.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the optional build_env metadata field: the names and versions of
the tools that created the package tarball. Hex records its version
there with hexpm/hex#1252, so the version needed to rebuild a package and
compare checksums can be read from the package alone.
Add recommendations to the package tarball spec for creating tarballs
whose bytes only depend on the files and the tool versions: entry order,
timestamps, owners, modes, NFC names, the gzip header and the order of
metadata keys. They describe what hex_core does since hexpm/hex_core#228.
They aren't requirements, and different tools aren't expected to produce
the same bytes as each other.