Skip to content
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

removed julia binary #619

Closed
wants to merge 1 commit into from
Closed

removed julia binary #619

wants to merge 1 commit into from

Conversation

zmjones
Copy link
Contributor

@zmjones zmjones commented Jun 25, 2013

it would be better to install julia as a binary from a normal homebrew formula, since it is also distributed as source. this formula creates a name conflict with this tap.

@vitorgalvao
Copy link
Member

I don’t find that a compelling argument. We have other duplicates with homebrew (avidemux, chicken of the vnc, macvim), and I don’t see why that would constitute an issue. Not only does it mean we sometimes can bring the apps to the hands of users sooner (it was the case with avidemux), it also means a user can choose to install either an already compiled executable (fast to get) or have it compiled from source (slow).

I haven’t tried it, but I’m thinking the conflict shouldn’t be too hard to solve (after all, we have those aforementioned casks, and as far as I know, they never posed a problem). You’re also acting on the assumption that users use that particular tap, which may very well not be the case.

If you could please explain what exactly are the messages pertaining to the conflict, we can try to solve the problem, but removing the cask doesn’t seem to me like the correct way of handling it.

@zmjones
Copy link
Contributor Author

zmjones commented Jun 25, 2013

Ok fair enough.

The error occurs when I execute brew tap staticfloat/julia which generates a warning Warning: Could not tap staticfloat/julia/julia over phinze/cask/julia. Homebrew then doesn't seem to recognize the formula. The formula is downloaded but brew install julia results in Error: No available formula for juila

@vitorgalvao
Copy link
Member

I don’t get that error, but I suspect what might be wrong (which would be easy and quick to fix). Could you please give me the output of brew doctor?

@zmjones
Copy link
Contributor Author

zmjones commented Jun 25, 2013

Error: Failed to import: codebug
Error: Failed to import: command-q
Error: Failed to import: foto-magico
Error: Failed to import: julia
Error: Failed to import: onyx
Error: Failed to import: papers
Error: Failed to import: postbox
Error: Failed to import: quick-hue
Error: Failed to import: renamer
Error: Failed to import: shimo
Error: Failed to import: shoes
Error: Failed to import: sql-editor
Error: Failed to import: unison-usenet
Error: Failed to import: zepheer
Your system is ready to brew.

@vitorgalvao
Copy link
Member

Yep, seems like good news. Run the following one-liner
ls -l /usr/local/Library/Formula | grep phinze-cask | awk '\''{print $9}'\'' | for evil_symlink in $(cat -); do rm -v /usr/local/Library/Formula/$evil_symlink; done

And that’s it, really, it should work now. After you run brew install julia again, you should see

Error: julia is a head-only formula
Install with `brew install --HEAD julia

And after running brew install --HEAD julia, it should work.

To explain what’s going on, the above code is from this comment, and is meant to fix this problem which occurs due to this issue.

Can you confirm everything now works for you as intended?

@zmjones
Copy link
Contributor Author

zmjones commented Jun 26, 2013

yep that totally does. thanks for the help.

@zmjones zmjones closed this Jun 26, 2013
@zmjones zmjones deleted the rm-julia branch June 26, 2013 00:10
@vitorgalvao
Copy link
Member

No problem. Glad to see it was an easy fix.

@ghost ghost mentioned this pull request Jul 26, 2017
4 tasks
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants