docs: use canonical release epoch
This commit is contained in:
parent
4741d34783
commit
f6bbb95eee
1 changed files with 6 additions and 5 deletions
|
|
@ -84,14 +84,15 @@ the result before moving it to its destination. Exporting the tree rather than
|
||||||
the commit omits Git's commit-ID PAX header:
|
the commit omits Git's commit-ID PAX header:
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
SOURCE_DATE_EPOCH="$(git show -s --format=%ct HEAD)" \
|
make DIST_TARBALL=/tmp/zupt-5.2.8.tar.gz dist
|
||||||
make DIST_TARBALL=/tmp/zupt-5.2.8.tar.gz dist
|
|
||||||
sha256sum /tmp/zupt-5.2.8.tar.gz
|
sha256sum /tmp/zupt-5.2.8.tar.gz
|
||||||
```
|
```
|
||||||
|
|
||||||
With identical committed input and `SOURCE_DATE_EPOCH`, repeated exports must
|
The canonical release uses the tracked `.source-date-epoch`; an explicit
|
||||||
have the same SHA-256 digest. Do not generate a release tarball from uncommitted
|
`SOURCE_DATE_EPOCH` override intentionally creates a different archive. With
|
||||||
working-tree files.
|
identical committed input and epoch, repeated exports must have the same
|
||||||
|
SHA-256 digest. Do not generate a release tarball from uncommitted working-tree
|
||||||
|
files.
|
||||||
|
|
||||||
The AUR, Homebrew, and Guix recipes pin the checksum of this tarball. They are
|
The AUR, Homebrew, and Guix recipes pin the checksum of this tarball. They are
|
||||||
marked `export-ignore` in `.gitattributes` so their own checksum fields do not
|
marked `export-ignore` in `.gitattributes` so their own checksum fields do not
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue