| Age | Commit message (Collapse) | Author | 
|---|
|  | This avoids issues where a gem is installed but cannot be found.
Fixes #3355.
Fixes #3760. | 
|  | Otherwise running on old casks can produce deprecations.
Fixes #3738. | 
|  |  | 
|  | Fix the code so we don't actually output `odeprecated` warnings for
`HOMEBREW_CACHE`d or `.brew`d formulae. | 
|  | `HOMEBREW_CACHE`d and `.brew`ed formulae cannot be updated so don't
complain about their deprecation. | 
|  | Rather than just telling them to submit an issue as it's likely that
as these folks will be able to submit a PR. | 
|  |  | 
|  | The method with_system_path is no longer needed,
since environment filtering uses a default PATH. | 
|  | Specifying an absolute path to utilities is no longer needed,
since environment filtering uses a default PATH. | 
|  | - Don't allow taking an argument. This doesn't work and never has as it
  caches the result regardless of the argument.
- Don't rely on the PATH to check for external commands. | 
|  |  | 
|  | - Use it in more places where it saves code
- Allow using symbolic keys for a cleaner interface
- Use `HOMEBREW_GEM_*` instead of `GEM_OLD_*` | 
|  |  | 
|  |  | 
|  |  | 
|  | `brew cask list` supports the `--full-name` flag which will include the tap
name for casks not part of the core caskroom/cask tap. For example, if
cask "foo-beta" is installed from the caskroom/versions cask, `brew cask
list --full-name` will report the name as "caskroom/versions/foo-beta". | 
|  |  | 
|  | It's been long enough that these have been commented out so let's
enable them globally. | 
|  |  | 
|  |  | 
|  |  | 
|  | rubocop: don’t allow Perl regex backrefs. | 
|  |  | 
|  |  | 
|  | Add `atom` (not my editor of choice [TextMate for life!]) but widely
used enough to probably warrant it. Also, reorder based on my best
guestimates of current usage and cleanup the editor code while we're
here. | 
|  |  | 
|  | fixes #2709 | 
|  |  | 
|  |  | 
|  | Remove `to_s` from some `Pathname`s. | 
|  | - only document HOMEBREW_* variables in the manpage (although still
  read from all the original environment variables).
- resort manpage environment variables in alphabetical order
- check the original path for trailing slashes | 
|  |  | 
|  | This reverts commit 3e4547f52e7ebec633f8bfefc8a396d944edf908, reversing
changes made to 6edf9382bcc1240ad6f97c8b752cfe56cef9965d. | 
|  | This reverts commit 2372872974d1049c2beafe7dedb7f8f882502058, reversing
changes made to 3e4547f52e7ebec633f8bfefc8a396d944edf908. | 
|  | If people have `HOMEBREW_RUBY_PATH` set then things explode in a rather
confusing fashion. Instead, run `bundle` for them with the arguments
that they'd want.
Also, move `macho` requires into the module itself; it's a pain having
to do everything for Bundler before requiring `pathname` which is a core
Ruby class. | 
|  | Homebrew's actually ended up using a fair few gems. While we want to
avoid Bundler at runtime (and this PR still does that, in fact uses
Bundler even less at runtime than it did before) writing our own version
to use at build-time seems redundant. | 
|  |  | 
|  | It may not exist before Gem installation which means that the resulting
installed gem will not be found in the PATH. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | I wasn’t aware this existed when I created puts_hash so: may as well
remove it. | 
|  | Handle cases like e.g. `EDITOR="subl -w"`. | 
|  | Another attempt at fixing `brew audit` issues around detecting
`revision` and `version_scheme` changes correctly. First done in #1754
and #2086 (reverted in #2099 and #2100).
To ease future debugging a `ph` helper has been added to print a hash
and a series of RSpec tests to verify that the `revision`,
`version_scheme` and `version` formula version audits behave as
expected.
Fixes #1731. | 
|  | Hide sensitive tokens from install/test/post. | 
|  | Handle when there's no editor variable specified or it's specified but
empty. | 
|  | Hide these tokens to avoid malicious subprocesses e.g. sending them
over the network. Also, support using these tokens with environment
filtering and clear `HOMEBREW_PATH` from subprocesses to stop them
sniffing it. Finally, use `HOMEBREW_PATH` to detect Homebrew’s user’s
PATH for e.g. `brew doctor` etc. | 
|  | For many people `brew edit` makes use of the `EDITOR` variable to pick a
sensible editor. With environment filtering enabled unless this editor
is found in the default system PATH it'll fall back to e.g. `vim`.
Instead, ensure that we export the original, pre-filtering `PATH` as
`HOMEBREW_PATH` and use that internally to locate the editor. In future
this same approach will likely be used for requirements to be able to
find tools, too, and for other variables which we want to expose to
Homebrew itself but not other build tools.
Note that `HOMEBREW_PATH` is the same as `PATH` when build filtering
hasn't been enabled. |