You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is a solid path, but for many macOS developers, brew install ... is the default expectation for CLI tools.
Why discuss this
lower installation friction for macOS users already using Homebrew
provide a familiar install/upgrade/uninstall workflow
improve discoverability for users who may not already know uv
keep uv as the main path while offering Homebrew as an additional option
Possible directions
Maintain an official Homebrew tap.
Package from PyPI or tagged GitHub release artifacts.
Add Homebrew to the README as an optional install path, not a replacement.
Revisit Homebrew/core only if maintenance burden stays low.
Open questions
Is the release process already compatible with Homebrew packaging?
Would maintainers be open to an official tap, or is this out of scope?
If contributions are welcome, are there packaging/versioning constraints contributors should account for?
I previously opened an issue for this topic, but this seems better suited to Discussions since it is mainly a product/distribution conversation rather than a concrete bug report.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to open a discussion about supporting Homebrew as an additional installation path for
spec-kit/specify-cli.The current README primarily recommends:
That is a solid path, but for many macOS developers,
brew install ...is the default expectation for CLI tools.Why discuss this
uvuvas the main path while offering Homebrew as an additional optionPossible directions
Open questions
I previously opened an issue for this topic, but this seems better suited to Discussions since it is mainly a product/distribution conversation rather than a concrete bug report.
Related issue: #1903
Beta Was this translation helpful? Give feedback.
All reactions