Add note & CI on reproducible builds for macOS

Author: xxuejie

.github/workflows/rust.yml

@@ -176,6 +176,8 @@ jobs:
         submodules: true
     - name: Install llvm 16
       run: brew install llvm@16
+    - name: Install coreutils
+      run: brew install coreutils
     - name: Install riscv64 target
       run: rustup target add riscv64imac-unknown-none-elf
     - name: Install cargo generate
@@ -195,6 +197,8 @@ jobs:
         git submodule add https://github.com/xxuejie/lib-dummy-atomics deps/lib-dummy-atomics
     - name: Run all checks
       run: cd test-workspace && make build test check clippy
+    - name: Reproducible build runs
+      run: cd test-workspace && ./scripts/reproducible_build_docker --update && ./scripts/reproducible_build_docker --no-clean
     - name: Generate standalone contract
       run: cargo generate --path . standalone-contract --name test-contract
     - name: Run all checks

README.md

@@ -173,7 +173,7 @@ The templates provided here, use the same conventions as `ckb-native-build-sampl
 
 ### Reproducible Build
 
-When using this set of templates, we always recommend to use locally installed native versions of LLVM & Rust to build and test your scripts. However, reproducible build is an important part of CKB scripts, which would require locked versions of LLVM & Rust to work, which might not be an easy task when using locally installed versions of compilers.
+When using this set of templates, we always recommend to use locally installed native versions of LLVM & Rust to build and test your scripts. However, reproducible build is an important part of CKB scripts, which would require locked versions of LLVM & Rust to work. It might not be an easy task when using locally installed versions of compilers.
 
 For the time being, we have prepared a script that does reproducible build via [a docker container image](https://github.com/cryptape/llvm-n-rust). We do want to mention that docker is not necessarily THE way to do reproducible build, nor is it the best way to do reproducible build. There might well be other ways that are better, such as chroot or Nix. It's just that historically, docker has been used in CKB script's build process, and adding a script leveraging docker here, provides an easy solution into the issue.
 
@@ -195,6 +195,12 @@ $ ./scripts/reproducible_build_docker --proxy "..." # Setup docker container so
 
 By default, the checksum file is stored in `checksums.txt` in the root of the repository. It is strongly recommended that this file is checked into version control, and a CI is setup so reproducible build is always checked in new commits.
 
+Note that reproducible build here relies on the presence of `sha256sum` command, if you are using macOS, you can install it via the following command:
+
+```
+brew install coreutils
+```
+
 ### Standalone Contract Crate
 
 In rare cases if you want to simply use a standalone contract crate without a workspace. The [standalone-contract](https://github.com/cryptape/ckb-script-templates/tree/main/standalone-contract) template is prepared for you: