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.

Sign up for GitHub

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

Jump to bottom

Not linking casks makes brew doctor complain #89

Closed
phinze opened this issue Oct 28, 2012 · 3 comments · Fixed by #56115
Closed

Not linking casks makes brew doctor complain #89

phinze opened this issue Oct 28, 2012 · 3 comments · Fixed by #56115

Comments

@phinze
Copy link
Contributor

phinze commented Oct 28, 2012

Running brew doctor will yell at you about your casks since it thinks they're not linked.

What should we do about this?

  • Ask upstream to loosen requirements to prevent warnings?
  • Do something to pretend like we're linked?
  • Avoid the Cellar altogether?
@SeanTAllen
Copy link
Contributor

I think the 3rd is probably the most reasonably.

/usr/local/Caskroom ?

@phinze
Copy link
Contributor Author

phinze commented Oct 28, 2012

Yeah it's looking like that might be the best option - especially since I find myself writing our own uninstall link etc. We're piggy backing on less and less of Homebrew's code.

Gonna think about it a bit more before I make any big moves - maybe spike it out in a branch. Stay tuned. 📻

@passcod passcod mentioned this issue Dec 10, 2012
Closed
@passcod
Copy link
Contributor

passcod commented Feb 18, 2013

Done in 9189bd5 (moved to Caskroom).

@passcod passcod closed this as completed Feb 18, 2013
fharbe pushed a commit to fharbe/homebrew-cask that referenced this issue Mar 11, 2014
@fanquake
Merge pull request Homebrew#89 from olegafx/patch-2
f4bfd44 
PhpStorm-EAP 133.626
@miccal miccal removed the bug Issue describing a reproducible bug. label Dec 23, 2016
@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.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update Vorta to v0.6.1
4 participants
@phinze @passcod @SeanTAllen @miccal