Code-with-Rudro commented on issue #1847: URL: https://github.com/apache/camel-website/issues/1847#issuecomment-6883293078
Hi @davsclaus , I'd like to take part 3 of this issue (the website change) and be assigned to it. My understanding: `content/download/camel-cli-launcher.md` should gain a "Package managers" section, with Homebrew only for now. It should also say that `camel self-update` doesn't update a Homebrew install (`brew upgrade apache-camel` does), and link the install guide for `camel doctor`. I see this depends on the homebrew-core formula being merged first, so I would keep the PR as a draft until then. To make review easy, this is the text I'd propose (based on the 4.23.0 formula and your test results above): > ## Package managers > > ### Homebrew (macOS) > > brew install apache-camel > > This installs the `camel` command and JDK 21 (`openjdk@21`) if needed. Upgrade with `brew upgrade apache-camel`; `camel self-update` does not update a Homebrew installation. If several installations exist, `camel doctor` lists them and marks the active one. See [Installing the Camel CLI Launcher](/manual/camel-jbang-launcher-install.html). I've limited it to macOS because that is the platform you tested. I'll adjust the wording to match the final formula and the page's existing heading and link style (the site's HTML check requires relative links). Validation: `yarn build` and `yarn preview` locally, then `CAMEL_ENV=production yarn checks`, then the Netlify preview. If assigning it now is fine, I'll open the draft PR. If you'd rather wait until the formula is merged, I'm happy to wait and will keep an eye on the homebrew-core PR. Thanks! <img width="1672" height="941" alt="file_000000001fdc8208a9a99d4e25f4c069" src="https://github.com/user-attachments/assets/9edcbbf3-c977-4330-9266-612b5cc53d02"; /> -- 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]
