| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Hiding all output makes it look like Homebrew is hanging while the tap
operation (which can take a long time!) is running.
Closes #3053.
|
|
I just ran into an issue where a colleague's Homebrew couldn't update.
It seems to have been because it failed once just after the new repo
directory was created. Since there was nothing in this directory, there
really isn't any reason for us to fail here, so to avoid this problem in
the future, try to `rmdir` the directory before failing because it already
exists.
|
|
May as well use the more secure link when possible.
|
|
|
|
These were those migrated from other taps but if they are installed
already: they aren't new to that user.
|
|
This avoids needing to use `force: true` and still let's Homebrew do
what we want with our own taps.
|
|
Migrate between different taps and delete relevant subdirectories if
they can be safely. Also, tweak some naming and use utility methods.
|
|
Check if `HOMEBREW_CELLAR/old_name` is a symlink. If so, it's already
been migrated so can be skipped.
|
|
update-report: migrate all formulae every time.
|
|
Unmigrated formulae cause hard-to-debug issues and relying on detection
on Git alone is faster but not comprehensive. Instead, iterate through
renamed, installed formulae every time and migrate them.
Closes #1770.
|
|
The taps they were migrated to are auto-tapped if not already tapped
anyway so don't show them as deleted to avoid confusion.
|
|
|
|
install tap cmd completions
|
|
Taps can include completion scripts for external commands under
`completions/bash`, `completions/fish`, or `completions/zsh`. `brew tap`
will automatically install these into the correct directories during
install.
|
|
migrating a formula to a cask.
|
|
|
|
Imports from homebrew/versions are migrated from that tap and then
renamed immediately when they hit homebrew/core. This did not trigger
our previous rename detection so address these to improve the output and
handle migration correctly.
|
|
Allow `tap_migrations` entries to have a `user/repo/formula` or
`user/repo/cask` format for migration of formulae to/from casks.
|
|
This is used by the install script so it can simplify it's logic and
make the analytics messaging more prominent.
|
|
There were some bugs with the use of `HOMEBREW_NO_ANALYTICS_THIS_RUN`
and some output glitches I missed with the previous PR (#1575).
|
|
- Don't output the analytics message and mark it as read if
`HOMEBREW_NO_ANALYTICS_THIS_RUN` is set. This mostly simplifies the
installer code where we can display the message ourselves there rather
than having `brew update` print it out sometimes and not others (i.e.
when there's no system Git installed).
- Use the shell's audible bell to nudge people to actually read this
message (and give them less excuse to complain when they don't).
- Add an extra newline and bold all the analytics messaging so it's
more visible in the output.
|
|
Look at HOMEBREW_PREFIX rather than HOMEBREW_REPOSITORY for the default
Caskroom location.
|
|
|
|
|
|
Use `module_function` for `Homebrew` module.
|
|
Fix updating the `stable` branch used for tagged updates and ensure
that the core tap isn’t retapped (the slowest part by far of this test).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If we have a `brew.sh` which has set
`HOMEBREW_ENABLE_AUTO_UPDATE_MIGRATION` then let's allow an auto-update
migration. That's because it contains the fix below it _before_ the
update happened which means the auto-update won't fail in the same way
as if updating from an old version.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
References #1023.
|
|
update-report: migrate everyone to new repository.
|
|
This will hang around otherwise due to e.g. running `bundle install` in
here once.
|
|
Before stashing also try to cancel any current merge, rebase and
reset. This will prevent any data loss but also make the stash more
likely to succeed.
|
|
update-report: also create Cellar on migration.
|
|
Just on the off chance it doesn't exist (i.e. no-one has installed
anything yet or you're a `test-bot` that's run `git clean -xdf`
recently)
|
|
This shouldn't be possible to occur after #1013 but it makes sense to
add it anyway.
|
|
Otherwise if they are created and empty they may be removed again
before we try to create the `/usr/local/bin/brew` symlink.
|