Toolchain: Fix package installing issue

[Growl1234]

• Fix some regression brought by Toolchain 202601 #7310 which would cause installation failure of packages using commit sha256 as version tag, and use the first seven characters of rather than full commit sha256 to meet the original intend.
• Introduce "retrieve_package" functional to manage package downloading. The main difference is that if file exists but checksum is incorrect it will be deleted and re-downloaded. This will prevent the failure when package downloading failed at the first run but a second try is executed without manually deleting the error tarball.
• Use tarball (tar.gz) for all architectures when installing CMake.

[Copilot]

Pull request overview

This PR adjusts the toolchain stage4 GitHub tarball installation logic to address failures introduced in the Toolchain 202601 update (#7310) when packages are pinned to specific commits, by switching those pins to use 7-character commit prefixes.

Changes:

• Shorten several commit-pinned package version strings in package_versions.sh from full commit hashes to 7-character prefixes.
• Update stage4 install scripts’ “commit vs tag” URL construction logic to treat 7-hex strings as commit refs.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
toolchain/scripts/stage4/install_rapidjson.sh	Updates commit-ref detection, but currently removes short_ver initialization while still using it later.
toolchain/scripts/stage4/install_libri.sh	Updates commit-ref detection, but currently removes short_ver initialization while still using it later.
toolchain/scripts/stage4/install_libcomm.sh	Changes install dir/tarball naming to use libcomm_ver directly and updates commit-ref detection.
toolchain/scripts/stage4/install_cereal.sh	Changes install dir/tarball naming to use cereal_ver directly and updates commit-ref detection.
toolchain/scripts/package_versions.sh	Shortens commit-pinned versions (cereal/libcomm/libri/rapidjson/nep) to 7-character prefixes.

Comments suppressed due to low confidence (2)

toolchain/scripts/stage4/install_libcomm.sh:61

• The commit-ref detection regex only matches exactly 7 hex characters. If libcomm_ver is provided as a full 40-char commit hash, this will construct .../tar.gz/v<sha> and fail to download. Consider accepting both short and full commit hashes (or normalizing to short) before URL construction.

        # url construction rules:
        # - Branch names (master, main, develop) without v prefix
        # - Version tags (e.g., 1.0.0) with v prefix
        if [[ "${libcomm_ver}" =~ ^[0-9a-f]{7}$ ]]; then
            url="https://codeload.github.com/abacusmodeling/LibComm/tar.gz/${libcomm_ver}"
        else
            url="https://codeload.github.com/abacusmodeling/LibComm/tar.gz/v${libcomm_ver}"
        fi

toolchain/scripts/stage4/install_cereal.sh:57

• The commit-ref detection regex only matches exactly 7 hex characters. If cereal_ver is a full 40-char commit hash, the script will incorrectly treat it as a tag and construct .../tar.gz/v<sha>, causing download failure. Consider accepting both short and full commit hashes (or normalizing to short) before constructing the URL.

        # url construction rules:
        # - Branch names (master, main, develop) without v prefix
        # - Version tags (e.g., 1.0.0) with v prefix
        if [[ "${cereal_ver}" =~ ^[0-9a-f]{7}$ ]]; then
            url="https://codeload.github.com/USCiLab/cereal/tar.gz/${cereal_ver}"
        else
            url="https://codeload.github.com/USCiLab/cereal/tar.gz/v${cereal_ver}"
        fi

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[QuantumMisaka]

LGTM
In fact I'm also trying to fix the problem, but this fix is better than mine \o/

[mohanchen]

Great, thanks for your help!