-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI: Include unitctl in our Homebrew and Linux packages #1281
Comments
@thresheek Please correct me if I am wrong, but this is complete yes? |
We have unitctl in homebrew (downloaded from GH releases), but not in the packages. I'm not sure if the approach taken in homebrew - downloading binary packages without building those - is applicable to Linux packages where we compile it all from scratch. This needs to be figured out. |
When we include unitctl in packages, we probably should build it from scratch if possible. However, it's an end-user tool, so for the next release or two it's fine to direct people to manually grab a binary from GitHub. |
FWIW, Rust will become a build requirement once we merge OpenTelemetry support for 1.34 (targeting late January 2025 for release), so work here should also get reused for that :) |
Rust is already a build requirement due to wasm modules we ship in the binary packages; same for Java / maven. I think it's just a matter of spending time on implementing the actual build process in packages and testing it on the supported OSes. |
Ah, yes, of course. Sorry, that completely skipped my mind. |
unitctl should also be built and published to the linux package managers that we build unit packages for, as well as homebrew
The text was updated successfully, but these errors were encountered: