-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Don't require/recommend ownership of /usr/local. #896
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
Conversation
Are we suggesting anything for the Other than those two questions, seems reasonable 👍. |
@DomT4 Caskroom is in HOMEBREW_REPOSITORY actually (which feels a little weird but is nice to avoid another root directory). Good call about |
👍 on the change. Not directly related to this PR, but what about adding a warning on what
The reason is that |
@zmwangx In my experience the longer you make these type of messages the less likely they are to be read. As we don't run them for users and they are recommendations I'm 🆒 with just trusting users . |
True 😓 |
Apple reset this on every OS X major (and some minor) updates and it always proves a painful and unnecessary step. Instead just check the directories we actually care about are writable. This may mean if these directories do not already exist (although they are now created by the installed) that `brew link` will fail and require manual intervention but this seems to be superior for both new and the majority of existing users.
@MikeMcQuaid looks like this broke CI. https://bot.brew.sh/job/Homebrew%20Core%20Pull%20Requests/7460/version=yosemite/console for everything ... |
Fix in #899. |
Previously Homebrew was installed into /usr/local directly. Now it installs into /usr/local/Homebrew by default. This does the same. See Homebrew/install#60 and Homebrew/brew#896 for more discussion on why Homebrew changed.
brew tests
with your changes locally?Apple reset this on every OS X major (and some minor) updates and it always proves a painful and unnecessary step. Instead just check the directories we actually care about are writable.
This may mean if these directories do not already exist (although they are now created by the installed) that
brew link
will fail and require manual intervention but this seems to be superior for both new and the majority of existing users.