Live data from Hacker News

El Capitan and Homebrew

github.com

91–100 of 298 posts

Re: El Capitan and Homebrew

#91
post #60

Earlier quoted context omitted.

FHS ( https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard )

Can't see how that applies. Does FHS really say anything about the structure underneath /usr/local ? Besides which, the Mac's filesystem isn't FHS in the first place...

Does FHS really say anything about the structure underneath /usr/local

If you want to be strict about it, yes: http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s09.html

Re: El Capitan and Homebrew

#92
post #86

To be fair, homebrew shouldn't need to change perms, it should follow common unix standards or at least fit in with OSX rather than require a hack. For years I've felt homebrew should really use either /opt/ or ~/.homebrew/ by default.

I can't think of anything more standard than /usr/local/.

Re: El Capitan and Homebrew

#93
post #86

To be fair, homebrew shouldn't need to change perms, it should follow common unix standards or at least fit in with OSX rather than require a hack. For years I've felt homebrew should really use either /opt/ or ~/.homebrew/ by default.

I can't think of anything more standard than /usr/local/.

Making/assuming /usr/local is 0777 is definitely not though.

Re: El Capitan and Homebrew

#94
post #86

To be fair, homebrew shouldn't need to change perms, it should follow common unix standards or at least fit in with OSX rather than require a hack. For years I've felt homebrew should really use either /opt/ or ~/.homebrew/ by default.

I can't think of anything more standard than /usr/local/.

/opt/local is more correct

Re: El Capitan and Homebrew

#95
post #86

To be fair, homebrew shouldn't need to change perms, it should follow common unix standards or at least fit in with OSX rather than require a hack. For years I've felt homebrew should really use either /opt/ or ~/.homebrew/ by default.

What makes you think /usr/local isn't a 'common unix standard'?

Never used Homebrew, but taking ownership of /user/local as I understand it does by default, certainly isn't a 'common unix standard'.

Re: El Capitan and Homebrew

#97
post #56

Earlier quoted context omitted.

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.

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.

But his comment refers to the new OS changes I believe thus it's going to be a pain going forward.

Re: El Capitan and Homebrew

#98
post #95

Earlier quoted context omitted.

What makes you think /usr/local isn't a 'common unix standard'?

Never used Homebrew, but taking ownership of /user/local as I understand it does by default, certainly isn't a 'common unix standard'.

> certainly isn't a 'common unix standard'

Here I google.com it for you.

http://www.pathname.com/fhs/pub/fhs-2.3.html#THEUSRHIERARCHY

EDIT: Why is it okay to NOT look up a Standard and be uncertain in your comments when it can be found in 20 seconds tops on the Internet?

Re: El Capitan and Homebrew

#100

When I first read this I was a little pissed at Apple, but what if brew were to install everything to /brew? It doesn't need to install into /usr/local.

You'd run into exactly the same problem. Apple doesn't provide /brew in the default image, so something would have to create a new inode in /, and that something presumably requires SIP be disabled (assuming / is protected in SIP at least).

Even if it worked, you'd be no better off than just using ~/.homebrew or something like it. Their whole reason for wanting /usr/local is that (a) /usr/local/bin is in the default $PATH, and (b) it can be written to by a normal user. Using /brew gives up (a) anyway, so you may as well just put it in a user's home directory somewhere.

Post reply on HN