51–60 of 298 posts
I'm starting to regret upgrading...
El Capitan inclues a HUGE number of security fixes that you do want to have. https://support.apple.com/en-us/HT205267
Earlier quoted context omitted.
That would break the unix convention they are trying to follow, so then they might as well put it anywhere else as well.
What unix convention are you referring to?
Earlier quoted context omitted.
That's a common Unix practice to put system-wide stuff manually managed (as opposed to managed by the OS/distribution) in /usr/local.
Yep, I agree and that's where I install stuff on everything other than OS X. One distinction though, I think, is that most of the stuff I install on OS X I don't want to be available system-wide. I'm (typically) not using Homebrew to install daemons that run all the time or things that serve critical system/network functions, so I've never seen a reason to make them available to the entire system. I agree that goes a…
A while ago I floated the idea of having a separate, low-privilege "brew" user that installs things, with the brew command automatically switching to that user, but there was no interest.
Earlier quoted context omitted.
What unix convention are you referring to?
https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
To me, the fact that you are directed to install Homebrew to /usr/local is wrong since there's no guarantee how /usr/local is going to treated by Apple in the future and this is now an example of that. The only directory that Apple, probably, doesn't have control is your home directory. I've been using homebrew for a long time without issues because, in my opinion, I installed it on ~/homebrew. I wonder why is that s…
Now since many people say they never run into problems with nonstandard homebrew path, I'd like to give it a try too.
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 works fine.
Will homebrew switch the default install location out of /usr/local for new installations then? I doubt most developers will want to dive into recovery mode just to install wget.
you don't need to. You only need to if you have manually deleted /usr/local for some reason. /usr/local is exempt from system integrity protection. The only problem is that its owner gets reset to root on every OS update, whereas Homebrew wants its owner to be the Homebrew user. The advantage of /usr/local as the installation root is that /usr/local/bin is in the default PATH of the OS and that setting the PATH in a…
To me, the fact that you are directed to install Homebrew to /usr/local is wrong since there's no guarantee how /usr/local is going to treated by Apple in the future and this is now an example of that. The only directory that Apple, probably, doesn't have control is your home directory. I've been using homebrew for a long time without issues because, in my opinion, I installed it on ~/homebrew. I wonder why is that s…
ref: Apple keynote slide #35 on http://devstreaming.apple.com/videos/wwdc/2015/706nu20qkag/7...
The first thing I did after the upgrade was disabling SIP. Now my system acts exactly the same way before with all the goodies (except rootless) el capitan has to offer. Having root not able to write system stuff is good for people that like to blindly execute shell scripts from the internet but I think apple should add something that makes it easier for developers to disable it. I don't know if there is a new method…
Earlier quoted context omitted.
That would break the unix convention they are trying to follow, so then they might as well put it anywhere else as well.
What unix convention are you referring to?