RISC-V binaries

[IngwiePhoenix]

What new feature should Elvish have?

I just built Elvish on my VisionFive2 - and by verbatin this works out perfectly!

root@riscboi ~# go install src.elv.sh/cmd/elvish@latest
go: downloading src.elv.sh v0.20.1
go: downloading pkg.nimblebun.works/go-lsp v1.1.0
go: downloading github.com/sourcegraph/jsonrpc2 v0.2.0
go: downloading golang.org/x/sys v0.16.0
root@riscboi ~# elvish --version
0.20.1
root@riscboi ~# uname -a
Linux riscboi 6.6.0-g076ede06c00a #29 SMP Tue Feb 13 00:01:46 CET 2024 riscv64 GNU/Linux

So, since this works quite well, I wanted to request RISC-V (riscv64) binaries.

Output of "elvish -version"

0.20.1

Code of Conduct

• I agree to follow Elvish's Code of Conduct.

[krader1961]

This is a reasonable request but it requires that the CI/CD environment used by the project support that architecture. Although I've been contributing changes for several years I've never looked at how the pre-built binaries are built. I think it's done using https://cirrus-ci.org/ which, AFAICT, does not support Risc-V at this time. It's not obvious that the number of users running Elvish on Risc-V is large enough today to justify setting up a build environment on something like the https://cloud-v.co/ service.