-
-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
link and conflicts_with options do not work as expected #1442
Comments
The console output indicates you already have mysql@8.0 installed (the Do a The code paths are different for new installs/upgrades vs when already installed. The brew link step is only a '--force' and not an '--overwrite'. A new install should call with a As to why the exit status code is 0. Well it only cares about whether things are successfully installed. Rightly or wrongly, link and service state failures aren't considered as part of this. |
From the docs:
We want
mysql@8.0
installed and linked. So we have this in ourBrewfile
:This does not work. The linking fails. Here's what happens.
The linking fails. Also
brew bundle
incorrectly exits with status code0
for successful execution. This is not true.The docs reference a
-f
to force overwriting. This also does not work as expected. Thebrew link
step fails in the same way:Note the command still exits
0
even though a part failed.The only way to resolve the issue is to manually run
brew unlink mysql
prior tobrew bundle
. This apparently defeats the purpose of thelink
andconflicts_with
options.This issue seems similar to #932.
My Current bundle version
The text was updated successfully, but these errors were encountered: