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.
Git is a transport and storage mechanism for us so we don't want to
allow arbitrary customisation of this due to user issues e.g. #3664
and #3561.
Fixes#3664.
It's not possible to determine the difference between a non-keg-only
keg that failed to link and one that wasn't linked by us intentionally.
To avoid additional complexity of storing this logic in another place
let's back out this relatively new functionality; sticky keg-only links
is a better and more desirable behaviour anyway.
Rather than blocking the rest of the formulae from being installed by
`brew upgrade` print the requirement failure messages (already done) and
an error stating requirements weren't satisfied and then continue to
upgrade the rest of the formulae.
