Closed jayvdb closed 2 months ago
In addition to the general "install-action vs cargo-binstall" aspect addressed with at https://github.com/taiki-e/install-action/pull/514#issuecomment-2155840470 , the reason we want to use jaq
and xh
instead of jq
and curl
in our workflows is that our build process explicitly use jaq
and xh
, which are not identical to jq
and curl
, so that our product builds and V&V processes have as few non-Rust dependencies as possible. Especially with jaq
, we've had to adjust the queries so they are supported by jaq
.
Each and every non-Rust binary on our build workers needs extra paperwork, including "system" provided tools. And while https://github.com/rustsec/advisory-db tends to be very conservative, that is a good thing in my industry, there isnt an equivalent for C/C++ , so C/C++ binaries are not just extra paperwork - they require active monitoring of system library dependencies, instead of relying on the rustsec community.
Thanks for explanation, that makes sense.
It seems that the CI has hit rate limit of GitHub, so it's quite slow.
I have rebased the PR against main to fix the CI due to outdated cargo-binstall
https://github.com/01mf02/jaq , jq clone