reproducible builds

[nick1udwig]

Problem

#509

Solution

Don't include timestamps in archives

Testing

Build, output hash, then build again.

Docs Update

None

Notes

None

[nick1udwig]

On this branch:

$ cargo +nightly build -p kinode && ~/git/tg-notify/tg-notify.py 
...
$ sha1sum target/debug/kinode
6f6fa5f7569800c4d2cbb704c6512099a4c48e77  target/debug/kinode
$ touch kinode/packages/app_store/app_store/src/lib.rs 
$ cargo +nightly build -p kinode && ~/git/tg-notify/tg-notify.py 
...
$ sha1sum target/debug/kinode
6f6fa5f7569800c4d2cbb704c6512099a4c48e77  target/debug/kinode

[nick1udwig]

On develop:

$ cargo +nightly build -p kinode && ~/git/tg-notify/tg-notify.py
...
$ sha1sum target/debug/kinode
f221475ed5be6135d5576cb877744ab97cfa9ee3  target/debug/kinode 
$ touch kinode/packages/app_store/app_store/src/lib.rs 
$ cargo +nightly build -p kinode && ~/git/tg-notify/tg-notify.py 
...
$ sha1sum target/debug/kinode
a5e47334b662ff68ca48db658b53ca64a4fd38ef  target/debug/kinode

[dolled-possum]

--release builds are now fully identical from build to build. For example, from this commit, you will always get a byte count of 39771448 and a shasum of ba82424d3d8a9aac29e0d72903b3a63848a54dd5.