Which, in turn, provides them for `brew info --json=v1` so other tools
such as e.g. `brew bundle` can make use of this information.

These are used to determine whether or not a formula’s install was
specifically requested by a user and/or pulled in as a dependency.

Instead of `puts`ing when the failure occurs save it until the error
message and print a prose description of what the failure was and the
output from the command. This makes the output from failing tests
significantly easier to read.

Rather than all versioned formulae regardless. Oops.

This would have eliminated the need for Homebrew/homebrew-core#9000, for
instance.

This is used to indicate a formula is a version of another formula.
This will be used to provide a consistent interface for older formulae
versions and replaces the use of `conflicts_with`.

This is a temporary measure until:

- #1862 is merged
- I can a test on `brew uses` against every formula in the official
  taps to verify that exceptions are no longer raised.

…rmulae in recursive dependency expansion""

This reverts commit dc9819b8.

Fixes #1848 by sharing recursive dependency resolution between
dependencies and requirements.

Coincidentally, this also fixes the errors introduced by #1784 that
necessitated it being reverted in #1797.

Users may have this set, breaking grep's output.

Fixes #1430.

Fixes #1821

When a Requirement is converted to a Formula it should be listed under
the runtime dependencies.

This means that a `brew install $ALIAS` records the path accordingly
so  e.g. `Formula#full_installed_specified_name` returns the correct
path.

We're frowning on these now so may as well turn that into code.

These can now be done with just `brew upgrade`, like other upgrades.

Fixes #1818.

also allow higher stable versions with the same version prefix

When the first parameter to inreplace was an array, and the replacement
failed, InreplaceError would end up crashing with an undefined method
exception because the order of operations resulted in super not being
passed the value of the entire inject block.

Fixes #1817.

If satisfy returns a `Pathname` from `which` then we can use that to
infer a formula dependency from that `Requirement`.

Xcode can be installed anywhere but for most people it's in
`/Applications/Xcode.app` so just look there if `xcode-select` isn't
helpful before looking at Spotlight which can return weird results on
e.g. backup disks.

Fixes #1587.

Xcode can be installed anywhere but for most people it's in
`/Applications/Xcode.app` so just look there by default before looking
at Spotlight which can return weird results on e.g. backup disks.

We want to prefer the newer/versioned formulae when possible but this
is preferable to a random cached formula or, worse, no formula.

This means `brew info foo` will never complain that `foo` is a missing
formula.

Which, in turn, provides it for `brew info --json=v1` so other tools
such as e.g. `brew bundle` can make use of this information.

Unfortunately `brew linkapps` cannot behave nicely with e.g. Spotlight
using either aliases or symlinks and Homebrew formulae do not build
"proper" `.app` bundles that can be relocated. Instead, please consider
using `brew cask` and migrate formulae using `.app`s to casks.

`virtualenv_install_with_resources` will automatically define and
install a `setuptools` resource so this is unnecessary.

References https://github.com/Homebrew/homebrew-core/pull/8570

If it's not there, produce a nicer error.

Fixes #1805.

Since /tmp (the default HOMEBREW_TEMP) is a symlink to /private/tmp,
some build systems (like Parrot's) will attempt to use the realpath
instead of the literal /tmp we supply it with. This breaks the relocation
code, which only tested the literal HOMEBREW_TEMP and not its realpath.

This allows us to detect if homepages such as e.g. `aiccu` which
blocks `curl` are up or not.