-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
bowtie conflicts with bowtie from homebrew/science #743
Comments
Please refer to this issue, and see if it helps correct the problem. If not, please run |
Since both applications are called "Bowtie", I don't see an obvious solution to this problem, other than renaming one arbitrarily, which doesn't appeal to me. Suggestions? I think this situation is different than #619, since these are in fact two different software packages both named "bowtie". |
Yes, my question was if following the other issue would get rid of the warning (as it did there). Realistically speaking, once that’s done there’s no longer a problem, since to install apps with homebrew-cask you have to use the This means that both apps are installed with distinct commands, making the warning the only real issue, and a minor one, at that. In fact, I’ve just tapped homebrew/science to test, and there’s no problem at all. Following the instructions in #169 (particularly the last comment before it was closed), should take care of it. |
Thanks for the clarification, Vitor. Is it possible to tap phinze/cask without the symlinks in the first place? Perhaps brew could use a tap --no-symlink option. |
Well, it shouldn’t be a problem in the future (when I did the test just now, it wasn’t). I’m just waiting on @cooljeanius’s confirmation that the issue is solved on his side, to close this (at which point you’ll be able to close yours, too), since it likely only occurred due to timing. For some background, the solution in #169 came from a comment in a different issue, and was a fix to a known problem, that occurred due to the main homebrew project, and has been fixed recently, so new setups and setups that have that issue fixed and are updated, should not encounter the problem. |
What’s the status, @cooljeanius? Did you solve the problem with the instructions? |
The one-liner from that thread wasn't working for me, so I did it this way instead: |
Alright, I’ll close this, then. You should be able to do the same, @sjackman. If you have any further issues related to this, @cooljeanius, feel free to reopen the issue. |
When running
brew prune
, I run into this warning:One of the two should probably be renamed.
I also filed this issue with homebrew/science as homebrew/homebrew-science#263
The text was updated successfully, but these errors were encountered: