From b459ba7a833d7866bde9fd976acd64fea74a5620 Mon Sep 17 00:00:00 2001 From: Mike McQuaid Date: Fri, 23 Oct 2015 14:55:21 +0100 Subject: El_Capitan_and_Homebrew: a few updates. Firm up some of the wording and remove stuff given that 10.10.1 didn't reset permissions back. Closes Homebrew/homebrew#45267. Signed-off-by: Mike McQuaid --- share/doc/homebrew/El_Capitan_and_Homebrew.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/share/doc/homebrew/El_Capitan_and_Homebrew.md b/share/doc/homebrew/El_Capitan_and_Homebrew.md index af80d5d00..baa769b7f 100644 --- a/share/doc/homebrew/El_Capitan_and_Homebrew.md +++ b/share/doc/homebrew/El_Capitan_and_Homebrew.md @@ -4,9 +4,7 @@ Part of the OS X 10.11/El Capitan changes is something called [System Integrity SIP prevents you from writing to many system directories such as `/usr`, `/System` & `/bin`, regardless of whether or not you are root. The Apple keynote is [here](https://developer.apple.com/videos/wwdc/2015/?id=706) if you'd like to learn more. -One of the implications of SIP is that you cannot simply create `/usr/local` if it is removed or doesn't exist for another reason. However, as noted in the keynote, Apple is leaving `/usr/local` open for developers to use, so Homebrew can still be used as expected. - -Apple documentation *hints* that `/usr/local` will be returned to `root:wheel restricted` permissions on [every OS X update](https://developer.apple.com/library/mac/releasenotes/General/rn-osx-10.11/index.html). There is a `brew doctor` check in place to advise if permissions have slipped for whatever reason. +One of the implications of SIP is that you cannot simply create `/usr/local` if you have removed it. However, as noted in the keynote, Apple is leaving `/usr/local` open for developers to use, so Homebrew can still be used as expected. **If you haven't installed Homebrew in `/usr/local` or another system-protected directory, this document does not apply to you.** -- cgit v1.2.3