ic-wasm provides pre-built wasms, which is great, but there is a standard location for pre-built cargo builds. If we use the standard location, instead or in addition to the current location, we can use cargo binstall ic-wasm.
Note: Cargo quickinstall provides ic-wasm binaries but these are built by a third party, so users depend on the honesty and competence of the third party. The quickinstall developers are probably honest and competent, but why take the risk?
Note: I checked whether binstall supports uncompressed artefacts. The documentation didn't seem completely clear to me on this point so I simply tried it out. In the test it failed to install a bare executable but successfully installed the same executable packed in a .tar.gz.
Changes
Provide binaries in a location recognised by binstall.
Note: The traditional location is preserved, as some users may be relying on that URL in their workflow.
Request
Can we please make a release after this has been merged? Together with #35, the installation of ic-wasm should be significantly easier.
Motivation
ic-wasmprovides pre-built wasms, which is great, but there is a standard location for pre-built cargo builds. If we use the standard location, instead or in addition to the current location, we can usecargo binstall ic-wasm.Note: Cargo quickinstall provides ic-wasm binaries but these are built by a third party, so users depend on the honesty and competence of the third party. The quickinstall developers are probably honest and competent, but why take the risk?
Note: I checked whether binstall supports uncompressed artefacts. The documentation didn't seem completely clear to me on this point so I simply tried it out. In the test it failed to install a bare executable but successfully installed the same executable packed in a
.tar.gz.Changes
binstall.Request
Can we please make a release after this has been merged? Together with #35, the installation of
ic-wasmshould be significantly easier.