[GH-ISSUE #3336] [Feature Request] need freebsd arm64 release #2670

Closed
opened 2026-05-05 13:43:19 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @shallowinggg on GitHub (Feb 27, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3336

Describe the feature request

I have seen some releases for freebsd-x86, but I need freebsd-arm64 release so I can write install scripts for my Raspberry Pi, instead clone and compile locally. Thanks!!!

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @shallowinggg on GitHub (Feb 27, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3336 ### Describe the feature request I have seen some releases for `freebsd-x86`, but I need `freebsd-arm64` release so I can write install scripts for my Raspberry Pi, instead clone and compile locally. Thanks!!! ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [X] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:43:19 -06:00
Author
Owner

@fatedier commented on GitHub (Feb 28, 2023):

We don't want to provide pre-compiled binary files for every system and architecture unless there are a significant number of users for that system and architecture.

<!-- gh-comment-id:1447500676 --> @fatedier commented on GitHub (Feb 28, 2023): We don't want to provide pre-compiled binary files for every system and architecture unless there are a significant number of users for that system and architecture.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 31, 2023):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1491135647 --> @github-actions[bot] commented on GitHub (Mar 31, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2670
No description provided.