* Reapply dropped commit in https://github.com/Homebrew/brew/pull/16643
* Change bindings example as `protobuf` no longer has any
* Remove `name "foo"` in example
* Replace `Language::Python.setup_install_args` example with `pip`
* Add some hints for CMake and autotools scripts given common issue of
incorrect Python selection due to allowing multiple Python deps
* Add note that `.pth` files should be avoided due to contamination
Co-authored-by: Eric Knibbe <enk3@outlook.com>
Signed-off-by: Michael Cho <michael@michaelcho.dev>
- Move the guidelines from Homebrew/brew Maintainer Guide to
Maintainer Guidelines as they apply to all repositories.
- Clarify the guidelines to make it clear that the default option
should be to approve a PR, with or without comments.
- Note in the New Maintainer Checklist that the most important task for
maintainers is reviewing pull requests.
Co-authored-by: Issy Long <me@issyl0.co.uk>
Co-authored-by: Sam Ford <1584702+samford@users.noreply.github.com>
Co-authored-by: Eric Knibbe <enk3@outlook.com>
We already had `HOMEBREW_FORBIDDEN_LICENSES` but this commit adds
`HOMEBREW_FORBIDDEN_CASKS`, `HOMEBREW_FORBIDDEN_FORMULAE` and
`HOMEBREW_FORBIDDEN_TAPS` for also forbidding those.
Relatedly, add `HOMEBREW_FORBIDDEN_OWNER` and
`HOMEBREW_FORBIDDEN_OWNER_CONTACT` to allow customising these
messages.
There were no existing tests for `HOMEBREW_FORBIDDEN_LICENSES` so have
added more tests for all of these checks.
Co-authored-by: Bo Anderson <mail@boanderson.me>
- We should tell people to not report issues if they are running in an
unsupported configuration.
- We should tell people to run `brew update` before reporting issues if
they have `HOMEBREW_NO_AUTO_UPDATE` set.
- We should tell people to not report issues in more types of
exceptions.
- Warn people in `HOMEBREW_NO_AUTO_UPDATE` documentation.
- DRY up `brew.rb` exception handling.
Co-authored-by: Colin Dean <colindean@users.noreply.github.com>
DomT4 and the Homebrew maintainers have agreed that homebrew/autoupdate
is a better fit for not being an official tap and has been moved back
to his user account.
Documentation and code has been adjusted accordingly and it was added
to the list of interesting taps.
This was discussed at the AGM. It's no longer needed to avoid
"cluttering up clones" because most users use the API for our
main repositories now.
It should also simplify security work in future because we can assume
anyone who can create a branch on the main repository has write access
rather than e.g. having a hardcoded list of maintainers we rely on.
