CKB Pulse

全部经验 · Developer tooling · 从这里开始 · 术语表

Release asset names differ per CKB tool实践来自一次修复

来自一次修复 · 核对结果:部分正确 · 核对于 2026-11-19

ckb, ckb-cli and ckb-debugger use `<tool>_<tag>_<triple>[-portable].<ext>`, while fnn and ckb-light-client use `<tool>_<tag>-<arch>-<os>[-portable].tar.gz`. ckb-debugger ships .tar.gz on every OS with a `<stem>-sha256.txt` and has no x86_64 macOS build, and ckb-cli ships .zip on macOS and Windows with no sums file. Try an ordered list of candidate names, including portable variants, against the release's actual asset list.

为什么重要: A single fixed asset name returns nothing for fnn, ckb-light-client, zip-packaged ckb or ckb-cli, and portable-only builds, so the installer fails even though a usable binary is published.

概念
Other
证据
来自一次修复: 来自一个项目,已对照其提交核对
首次出现
2026-11-11
最近改动
2026-11-14
最近核对
2026-11-19
对照提交的核对结果
部分正确:核心属实,但有一部分表述松散或范围过宽

来源(2)

更多关于Developer tooling

查看此主题的全部 35 条

你维护这条经验的来源项目吗?请确认或纠正

引用这条经验
LusoCryptoLabs, "Release asset names differ per CKB tool", CKB lessons, https://pulse.lusocryptolabs.com/learned/tooling/release-asset-names-differ-per-ckb-tool, CC BY 4.0, last changed 2026-11-14.

取自公开提交,并对照每条经验的来源提交和项目当前代码做了核对。使用前请先读来源。 文本采用 CC BY 4.0:请署名 LusoCryptoLabs, CKB lessons,并附上经验的链接。 想修改或撤下某条经验?请提交 issue。