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
Formalise a policy on what features can be included in formulae (when is this fine, what dependencies would we want to avoid and why, etc.). This is a tracking issue to facilitate discussion and improve our documentation on what "extra" features we are generally okay with including, and when it is fine to do so – what's the minimum number of requests beyond which we include things, etc.
A clearly documented policy allows us to point users making feature requests to it, and also ensures standards are applied consistently across formulae and by all maintainers.
The text was updated successfully, but these errors were encountered:
we should have a (minimal) algorithm for this e.g. a number of requests that exceeds the number of (recursive) dependencies this would add
we should consider having some ${FORMULA}-full/${FORMULA}-minimal formulae for maximal/minimal cases of formula and keep ${FORMULA} for "the functionality that we need for dependencies in Homebrew itself". This would likely help make e.g. ffmpeg significantly smaller in terms of dependencies (allowing more usage in more formulae)
we should consider having some ${FORMULA}-full/${FORMULA}-minimal formulae for maximal/minimal cases of formula and keep ${FORMULA} for "the functionality that we need for dependencies in Homebrew itself". This would likely help make e.g. ffmpeg significantly smaller in terms of dependencies (allowing more usage in more formulae)
Sounds like that would require ${FORMULA} to be keg-only, in order to coexist with ${FORMULA}-full or ${FORMULA}-minimal. Alternatively, addressing Homebrew/brew#16398 might help resolve this in a user-friendly manner, where ${FORMULA} is pulled in as a dependency but users prefer ${FORMULA}-full for active use.
What were you proposing (and why)?
Formalise a policy on what features can be included in formulae (when is this fine, what dependencies would we want to avoid and why, etc.). This is a tracking issue to facilitate discussion and improve our documentation on what "extra" features we are generally okay with including, and when it is fine to do so – what's the minimum number of requests beyond which we include things, etc.
A clearly documented policy allows us to point users making feature requests to it, and also ensures standards are applied consistently across formulae and by all maintainers.
The text was updated successfully, but these errors were encountered: