ci: add Linux binary release for loong64, ppc64le, and riscv64 - #14044
ci: add Linux binary release for loong64, ppc64le, and riscv64#14044MingcongBai wants to merge 1 commit into
Conversation
Add Linux binary release targets for loong64, ppc64le, and riscv64, these are architectures that are available both as desktop and server products. It is also reasonable to assume that they are used by developers as host machines, where this CLI tool would have been used. This commit is made with the understanding that GitHub has no interest in limiting usage of hardware of architectures other than x86, x86-64, Arm32, and Arm64. Given that GitHub CLI is largely an architecture-agnostic tool (at least with its built-in functionalities), that adding binary releases is rather trivial with GoReleaser, that Golang support is quite mature (and actively maintained) for the three architectures above, and that i386 is still a supported architecture despite host machines of strictly 32-bit x86 architecture likely being even more obscure, so add them. Link: cli#14012 Link: cli#8611 Link: cli#9410 Link: cli#8612 Link: cli#3615 Link: cli#1724 Signed-off-by: Mingcong Bai <jeffbai@aosc.io>
|
Thanks for your pull request! While it doesn't meet all of our standard requirements, it appears to be a small, focused contribution and has been routed to the team for review. Note: We still encourage linking to an issue with the |
|
@MingcongBai historically, we closed the same PR request for ppc64le purely because we do not have the capacity to support it. We have no development or test infrastructure. All that said, I will take the discussion back to the team again about having a "barely supported" class of architectures. I do appreciate that there is still a lot of value for our users in having an officially built artifact. |
Thank you for this. It is good to have a separate class of architecture based on testing/product input, as is commonly practiced amongst Linux distros. .NET, as I understand it, does the same thing (calling some as "community-supported architecture"). I honestly don't think anyone would be mad at occasional bugs or inconsistencies and, more than likely, folks using these architectures would be happy to assist in making them work. Bottom line is - it is, as you said, clear that people are asking for it, and I think the next important step is to clarify on support tiers. |
Yeh, I understand that. We are somewhat limited in our capacity to review them in both time and infrastructure. My bigger concerns though are around time we would have to spend on issues that we might be forced to address such as security or license compliance. In any case, I've started a discussion internally, I'd sure like to support people here if it doesn't bring too much of a maintenance burden for us. |
Add Linux binary release targets for loong64, ppc64le, and riscv64, these are architectures that are available both as desktop and server products. It is also reasonable to assume that they are used by developers as host machines, where this CLI tool would have been used.
This commit is made with the understanding that GitHub has no interest in limiting usage of hardware of architectures other than x86, x86-64, Arm32, and Arm64.
Given that GitHub CLI is largely an architecture-agnostic tool (at least with its built-in functionalities), that adding binary releases is rather trivial with GoReleaser, that Golang support is quite mature (and actively maintained) for the three architectures above, and that i386 is still a supported architecture despite host machines of strictly 32-bit x86 architecture likely being even more obscure, so add them.
Link: #14012
Link: #8611
Link: #9410
Link: #8612
Link: #3615
Link: #1724
Authorship and follow-up
Who wrote this:
Who answers review comments: