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

Tell users to delete old caskroom if it exists #22387

Merged
merged 1 commit into from
Jun 25, 2016
Merged

Conversation

jawshooah
Copy link
Contributor

Changes to the core

Refs #22359

@jawshooah jawshooah added enhancement core Issue with Homebrew itself rather than with a specific cask. awaiting maintainer feedback Issue needs response from a maintainer. labels Jun 25, 2016
@adidalal
Copy link
Contributor

LGTM

@adidalal adidalal merged commit ba08fbb into master Jun 25, 2016
@adidalal adidalal deleted the jawshooah-patch-1 branch June 25, 2016 22:48
@adidalal adidalal removed the awaiting maintainer feedback Issue needs response from a maintainer. label Jul 2, 2016
@joewiz
Copy link
Contributor

joewiz commented Jul 2, 2016

As the OP states in #21913 says, it would be great to give crystal clear, fool proof directions for migrating to the new location. The discussion in that issue gave some ideas, but even the one that seemed to garner the most praise contained a syntax error. I've summarized the approach and corrected the code in the quoted portion below. Would you consider adding this?

To move your Casks to the new, recommended location, use this command:
mv /opt/homebrew-cask/Caskroom /usr/local
Please note that any casks installed prior to #13966 were symlinked rather than moved to their destinations, so you'll need to re-install those manually. To simply reinstall all Casks, use this command:
for cask in $(brew cask list); do brew cask install $cask --force; done;

@vitorgalvao
Copy link
Member

To simply reinstall all Casks, use this command:
for cask in $(brew cask list); do brew cask install $cask --force; done;

As has been said repeatedly, brew cask list is broken, you cannot rely on it. There’s no simple foolproof command to this migration. Best we can do is give guidelines, which is what we already do.

@joewiz
Copy link
Contributor

joewiz commented Jul 3, 2016

Ah, I didn't realize that. Thanks for the reference to #14058.

@miccal miccal removed core Issue with Homebrew itself rather than with a specific cask. enhancement labels Dec 23, 2016
lantrix added a commit to lantrix/boxen that referenced this pull request Feb 7, 2017
@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.

5 participants