5 ms·

Installed El Capitan yesterday. Process took almost half an hour. Afterwards, brew just gave me a warning to do "chown" to my usr/local. That's it. Everything w

• cbhl 11y ago
  I think the bigger headache will be the next time you buy a new Macbook with El Capitan or later installed on it, because you'll need to do a song and dance to create the /usr/local directory in the first place.
  • pilif 11y ago
    Not true. Even on a fresh install, /usr/local exists and is exempt from SIP
    • rimantas 11y ago
      Yes. I did a fresh install and homebrew had zero problems.
  • benihana 11y ago
    I bought a new Air in mid September. I was a little annoyed that documentation seemed out of date, but it took all of five minutes to fix this. No song and dance needed, just a sudo mkdir.
    • nkassis 11y ago
      But his comment refers to the new OS changes I believe thus it's going to be a pain going forward.
      • slowhands 11y ago
        I just installed brew on a brand-new El Capitan install with 0 problems.
  • lsaferite 11y ago
    A simple 'sudo mkdir /usr/local' won't work with SIP?
    • lsaferite 11y ago
      Wow... I just re-read the page and saw what you have to do to create /usr/local and that is insane. Reboot into recovery mode?!? W.T.F?
      • eddieroger 11y ago
        Most Mac users will never need to do this, and the short reboot cycle is, to many, worth the extra security rootless brings. It's hardly WTF.
        • lsaferite 11y ago
          Being required to reboot my computer into recovery mode just to add a directory is certainly a WTF worthy situation. BTW, thanks for the down vote?
          • oddevan 11y ago
            To add a directory to a system-protected directory. It's all about protecting the integrity of the installed system. If you don't like/want it, you can reboot into recovery, disable it, and leave it that way.
            • Karunamon 11y ago
              The integrity of the installed system could be violated by creating a directory? My system was plenty protected already - it had a root account with a password only I knew. This is just more annoying Apple gatekeeping.
              • _Ogre 11y ago
                Your system is much more secure with SIP in place because it makes big parts of your system immune to trojans and privilege escalation attacks, the two biggest ways malware creeps into your filesystem. It's not very difficult to disable (even permanently if you are inclined), and offers a big security boost. And yes, it is Apple "Gatekeeping"... the same gatekeeping that's kept OS X almost completely free of major hacks for over a decade. I don't consider that annoying but to each his own.
• kiernan 11y ago
  Wouldn't that mean any other users would be unable to use (or maybe just install or upgrade) homebrew stuff?
  • garretraziel 11y ago
    That's how Homebrew works. Other could use it but not install or upgrade. From Homebrew docs: https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/FAQ.md#why-does-homebrew-say-sudo-is-bad- https://github.com/Homebrew/homebrew/blob/master/share/doc/h...
• matwood 11y ago
  I had the same experience in the betas so I've been a little confused by all the problems people are experiencing.