- Don’t mention `brew home` or `brew options` as their output is in
`brew info` (and the `(…|…)` is weird.
- Use full length flags for `-v` and `-d` to make more obvious what
they are doing
- Don’t use `Developers`; instead point out it’s how you contribute
- Mention `brew commands` for `COMMAND` output (like we do with
`FORMULA` and `brew search`)
- Point towards `docs.brew.sh`
It's really noisy and too pedantic for us to use now but I got it
working locally and used `--fix` to generate #3981 so let's add it as an
option for now.
This can't be tapped on vanilla Homebrew/brew because things like e.g.
`GlibcRequirement` are missing. We will put this back when the Linuxbrew
to Homebrew migration is complete.
Allow at `install` (or `install --only-dependencies`) time to specify
that test dependencies should be installed. This will allow simplifying
code in `brew test-bot`.
This could also be made an environment variable if desired by
maintainers.
These specify that they are needed by the test block. This can be
combined with `:build` to ensure that this formula isn't uninstalled
by `brew test-bot` when running `test do` blocks on our CI.
I received the following error when attempting to use the `upgrade`
command on a tap:
$ brew tap teddywing/passextract https://github.com/teddywing/Passextract.git
$ brew upgrade --verbose teddywing/passextract/passextract
Updating Homebrew...
==> Upgrading 1 outdated package, with result:
teddywing/passextract/passextract 0.4.0
Error: Calling build.build_bottle? is disabled!
Use build.bottle? instead.
/usr/local/Homebrew/Library/Homebrew/cmd/upgrade.rb:121:in `upgrade_formula'
Or, even better, submit a PR to fix it!
Change the method call to use the (presumably) newer version.
- Rename repository to homebrew-portable-ruby
- Add a new Bintray repository using new name
- Add GitHub releases mirror and try to use it
- Tell people not to file issues if they can't connect to Bintray or
GitHub: we're not here to provide ISP/proxy support.
This has been a nightmare in terms of the complexity to our dependency
system and the whack-a-mole required on bugs. If a Requirement resolves
to a Formula it should just use `depends_on "formula"` instead. This
matches the effective behaviour all users of bottles (the vast majority
of users and installs) and what we're doing in Homebrew/homebrew-core.
