AWS SAM CLI Formula is incorrect #4290
Replies: 2 comments 2 replies
-
Homebrew core pip formula all install in a virtual environment so no problem there.
Is there a way to install that file only for the architecture of the host?
That is inconvenient but not really something Homebrew is responsible for.
No, it's an open source project that somebody wanted in Homebrew and they did the work to have it accepted. Upstreams documentation or workflows are of no concern in this. |
Beta Was this translation helpful? Give feedback.
-
We ship binary packages so
The CLI should still work if you are running a container of the same arch, so "completely breaks" seems like an unwarranted exaggeration here. Still, this is easy enough to fix; thanks for flagging it. Homebrew/homebrew-core#124616 |
Beta Was this translation helpful? Give feedback.
-
Output of
brew config
Output of
brew doctor
Description of issue
First off, I am not sure this is the right way to reach out. I was confused this didn't really fit any of the issues and that pointed me to discussions but couldn't find anything to fit this either. So if there is a better place, I am happy to move this to that location
I am one of the maintainer of AWS SAM CLI and was poking around the formula that was added to the Homebrew Core. A couple problems I noticed,
As a side comment: in creating the AWS SAM CLI Formula in the core repo, it breaks our customers. We have docs that tell customers to
brew tap
thenbrew install
. Customers use to this flow and install without providing the tap (which is common), now get the Core repos formula. Which degrades their experience and leaves them with a broken CLI. In the future, maintainers of the Core should reach out before adding. This allows for communication and for people to callout risks to action you (Maintainers of Homebrew) are taking.Beta Was this translation helpful? Give feedback.
All reactions