[Tentative Idea] Introduce the Option for Formula and Cask Contributors to Use a Version of Homebrew's API JSON Generated Locally from Git Repository Contents #5003
Unanswered
RandomDSdevel
asked this question in
Tap maintenance and brew development
Replies: 1 comment
-
I personally think adding an API to bump formulae and casks is a better way. Very few version bumps have to be handled outside of |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm partly hesitant to suggest this since it introduces an additional level of abstraction, and thus overhead, for:
other, less compelling motivating use cases,
HOMEBREW_NO_INSTALL_FROM_API
' set (along with 'HOMEBREW_NO_AUTO_UPDATE
') because they prefer to restrict Homebrew from making any network requests outside of 'brew update
' and automatic and manual invocations of 'brew fetch
' since they either:Suggestion Premise
Would it ever make sense at any point, as a potential future improvement, to have an alternative provider for the JSON API aside from https://formulae.brew.sh that instead generates it locally as needed using the core formula and cask taps' locally-cloned/-installed Git repositories as its backing store?
One potential thing to think about either in parallel or afterward:
brew generate-formula-api
' and/or 'brew generate-cask-api
' for the taps that they're working in?brew
' itself? A filesystem watchdog daemon available from some tap in a manner similar to external 'brew
' sub-commands?)Beta Was this translation helpful? Give feedback.
All reactions