davsclaus opened a new issue, #1847:
URL: https://github.com/apache/camel-website/issues/1847
## Problem
New users cannot install the Camel CLI with Homebrew today: `brew install
apache-camel` and `brew install camel` both fail with `No available formula`.
There is no Camel formula in homebrew-core and no Camel tap, and homebrew-core
has never had a pull request for one.
The download page `content/download/camel-cli-launcher.md` only covers
`install.sh` / `install.ps1`, and does not mention package managers at all.
## What exists in apache/camel
-
`dsl/camel-jbang/camel-launcher/src/jreleaser/distributions/camel-cli/brew/formula.rb.tpl`:
the formula that JReleaser renders at release time. It installs the
`camel-launcher-<version>-bin.zip` from Maven Central into `libexec`, runs
`bin/camel.sh` with a JDK 21+ (`depends_on "openjdk"`), and tests `camel
--version`. It has a `livecheck` on the `maven-metadata.xml` of
`camel-launcher`.
- The `posix-validator (macos-latest)` job of "Package-native validation"
taps the rendered formula locally and runs `brew audit`, install, `camel
--version`, `camel init` and uninstall.
- `src/jreleaser/bin/camel-publish.sh`: a release step that opens a pull
request against Homebrew/homebrew-core (`brew create` for the first release,
`brew bump-formula-pr` after). It has never been run.
- `jreleaser.yml` settles the name `apache-camel` in homebrew-core (as
`apache-flink`, `apache-spark`, `apache-arrow`), not a tap of our own. The
command stays `camel`.
## What is needed
1. **First formula in homebrew-core**, for a released version (the latest
launcher on Maven Central is 4.23.0): render the formula, check it with `brew
audit --new --strict --online` and `brew test` from a local tap, and open the
pull request against Homebrew/homebrew-core from a committer's own account.
Camel meets the notability rules, Homebrew accepts the binary distribution of a
Java application (as for `maven`, `gradle`, `tomcat`), and Camel K's `kamel` is
already in homebrew-core.
2. **Later releases**: once the formula is in homebrew-core, Homebrew's
autobump usually updates it from the `livecheck`, so `camel-publish.sh` may
only be needed for the first submission. To be confirmed after the first merge.
3. **This website**: once `brew install apache-camel` works,
- add a "Package managers" section to
`content/download/camel-cli-launcher.md` (Homebrew first, and SDKMAN, WinGet,
Scoop and Chocolatey as they become available), next to the installer scripts;
- say that `camel self-update` does not update a Homebrew installation
(`brew upgrade apache-camel` does), as the Camel CLI docs already say;
- link the Camel CLI documentation (`camel-jbang-launcher-install.adoc`)
for `camel doctor`, which lists several installations.
The alternative to homebrew-core is a tap repository
(`apache/homebrew-camel`, via an ASF INFRA request): no Homebrew review and we
control the releases, but users would run `brew install
apache/camel/apache-camel`.
_Claude Code on behalf of davsclaus (Claus Ibsen)_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
