| Age | Commit message (Collapse) | Author |
|---|
|
This allows querying multiple attributes in the same way as
`revision_map` did but without duplicating code or repeatedly traversing
history.
|
|
Assume Ruby 2
|
|
|
|
- ignore Cask's files in `readall` (for now, there's an intentional
syntax error that will need fixed)
- run Cask's tests if they exist
- don't check Cask's files in coverage reports (for now)
|
|
Enable sandbox by default for homebrew/core
|
|
- Inconsistent or unneeded indentation
- Missing or superfluous empty lines
- Missing or wrongly formatted arguments in command summary
- Missing punctuation
|
|
|
|
list: note that `ls` command is used.
|
|
Enable vendored Ruby 2.0.
|
|
|
|
|
|
|
|
And arguments can be passed through to it.
Tweak produced out of conversation in
https://github.com/Homebrew/brew-evolution/pull/8.
|
|
search: remove thread-unsafe Hash cache.
|
|
update: add --force argument.
|
|
`test-bot --ci-testing` supports a `--tap` option for non-core taps, so
`brew pull` should too when pulling Homebrew Testing jobs.
|
|
Doesn't appear to affect the speed of `brew search`.
Fixes #415.
|
|
Add a `brew update --force` to side-step all of the clever optimisations
we have to detect if an update is unnecessary. That means if those
optimisations go wrong in future we can tell people just to run this
single command.
This would have been a useful workaround for the issue fixed in 985c672.
|
|
UPSTREAM_BRANCH was being used both as a loop variable name and name
for the upstream branch for HOMEBREW_REPOSITORY. This meant that the
variable names were overwritten which prevented update.
Closes #693.
|
|
|
|
Otherwise this can prevent taps from being updated as expected.
|
|
|
|
|
|
|
|
|
|
|
|
This can just live in `brew.sh` and then it doesn’t need repeated in
all the other places.
|
|
Tweak the logic further to make the no-op case even faster.
Before:
```
brew update 1.10s user 1.05s system 92% cpu 2.325 total
brew update --preinstall 0.60s user 0.77s system 96% cpu 1.433 total
```
After:
```
brew update 0.60s user 0.34s system 83% cpu 1.132 total
brew update --preinstall 0.29s user 0.24s system 62% cpu 0.860 total
```
These times are now fast enough to avoid any further special-casing for
`--preinstall`, roll it out to users by default and not print a message
unless we've actually found some updates.
|
|
|
|
Fixes #671.
|
|
This is less than ideal but it gets the time on my machine down from ~6s
to ~2s when checking no taps. It still shows that we're doing way more
in `update.sh` than we need to be doing but that's a future PR.
|
|
|
|
|
|
e.g. Caskroom/homebrew-cask.
Thanks to UniqMartin for the fix.
Fixes #655.
|
|
Closes #648.
Signed-off-by: Dominyk Tiller <dominyktiller@gmail.com>
|
|
|
|
|
|
Introduce `--fetch-HEAD` option. Without this option upgrade and
outdated never fetch latest upstream commit to detect if HEAD is
outdated -- tabs are used instead. However, if option is passed,
we fetch commit from upstream, which is more time consuming,
but we can be sure that version is up-to-date or outdated.
|
|
No longer output every cask under the list of changed formulae but
instead create a dedicated, unprinted report section for casks and then
iterate through that instead.
|
|
|
|
This reverts commit b33b1af073979c8a699ed9688dba37fb7e74f0b5.
|
|
|
|
`any?` is not the opposite of `empty?`. Besides the case that
`[false, nil].any?` will return false, `any?`(O(n)) has much worse
performance than `empty?`(O(1)).
|
|
|
|
Rather than nudge people to run `--strict` and then ignore some of the
results sometimes (e.g. GitHub repository notability) instead add a
dedicated `--new-formula` option that implies this is a one-time
advisory check.
|
|
`--force` isn't quite what we want here as it'll just allow keg-only
linkage whereas we want to ensure we overwrite anything the Cask
installed.
|
|
Closes #588.
Signed-off-by: Mike McQuaid <mike@mikemcquaid.com>
|
|
|
|
This extends the approach in #597 to further prevent linkage of formulae
that conflict with the system OpenSSL and can cause the issues
described in that issue.
|
|
|
