Folder where the macos cli is installed is incorrect
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
**Describe the bug**
I am on a m2 mac machine. The homebrew installation path is `/opt/homebrew`. But, the keybase-related cli commands are being installed into `/usr/local/bin`.
**To Reproduce**
Steps to reproduce the behavior:
1. Install keybase on an arm mac using homebrew
2. Run the keybase client
3. In a Terminal session, list the files in the `/usr/local/bin` folder - and see that there's a different copy of the command (which is in effect a symbolic link to the same real execuable)
4. To be able to use the cli, I will then have to manually ensure that the zsh configuration files includes this folder in the PATH env var.
**Expected behavior**
Since the `/opt/homebrew/bin` folder is present in the local machine and the `PATH` environment variable includes that for arm machines, I would have expected the symlink also to be created in that folder.
**Screenshots**
If applicable, add screenshots to help explain your problem.
Version 6.5.1-20250422141116+19f9cfeddb (6.5.1-20250422141116+19f9cfeddb)
**Additional numbers**
The number 345567
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the installation on an ARM Mac with Homebrew and inspect where the Keybase CLI symlinks are created. Trace the macOS installation and CLI setup entry points to determine why /usr/local/bin is used instead of /opt/homebrew/bin; done means the CLI is available through the existing Homebrew PATH without manual zsh configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100