Live data from Hacker News

El Capitan and Homebrew

github.com

211–220 of 298 posts

Re: El Capitan and Homebrew

#211

Earlier quoted context omitted.

A. There is no real standard here B. Apple doesn't bend, period. They don't actually care whether the use is appropriate or inappropriate. C. Blaming this on homebrew is hilarious Remind me again why i should need to reboot into recovery mode to create a directory?

There is a standard: http://news.stanford.edu/pr/2015/pr-worms-digest-plastics-09... . This is from RedHat. Not implemented by everyone, but modern OSes (e.g. CoreOS) seem to follow the patterns. CoreOS also do everything in their power to prevent you from mounting /usr as writeable. Perhaps that doesn't pass your bar for 'real' though since it's not globally implemented ;)

I think that's the wrong link? (It's to a press release from Stanford's engineering department about plastic-eating worms...)

Re: El Capitan and Homebrew

#212
post #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…

/ is not protected by SIP.

Re: El Capitan and Homebrew

#214
post #200

Earlier quoted context omitted.

Agreed, I don't understand why so many people use homebrew instead of macports. Macports seems to be immune to so many issues that complicate homebrew, and I love that it keeps everything in its own dir, '/opt'. Easy to see what it installed, and easy to uninstall (rm -r /opt). The commands are also easier for me to remember -- no awkward, overstretched analogy. I often help people start hacking on open source projec…

"Agreed, I don't understand why so many people use homebrew instead of macports." This might seem very odd to you, and maybe I'm a weird outlier, but after having used macports for years, and installed it many times on many different systems, the requirement for full blown xcode is quite a turn-off and makes any alternative interesting and attractive. The OSX system I am typing on now should have macports on it, and…

Just FYI anyone can download XCode from the App Store, it doesn't require a "dev login". (Agree it would be nice if MacPorts only required the XCode Command Line tools like homebrew, it would be one less download.)

Re: El Capitan and Homebrew

#215
post #205
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.

> it should follow common unix standards Isn't /usr/local? > or at least fit in with OSX It did - before now /usr/local was available unprivileged with ownership. > rather than require a hack It only needs that now, since requirements to "fit in with OSX" have changed. That's not Homebrew's fault - they need a fast solution. Kudos in my book for responding before it's a problem.

No, /usr/local is normally 755 root:root (or whatever the effective equivalent is). Homebrew wants it to be 775 root:admin, so that users with the admin bit can write to it. That's not standard.

People keep writing here as if El Cap removes /usr/local entirely. It does not. /usr/local is there by default. You only have to go into recovery mode if you've somehow removed it yourself.

Re: El Capitan and Homebrew

#216

Why does homebrew install things as root anyway? Seems like defaulting to installing in your home directory would be a much better practice.

Homebrew does not advocate installing things as root. You can read more about it here: https://github.com/Homebrew/homebrew/blob/master/share/doc/h...

Re: El Capitan and Homebrew

#217

Why does homebrew install things as root anyway? Seems like defaulting to installing in your home directory would be a much better practice.

Homebrew does not advocate installing things as root. You can read more about it here: https://github.com/Homebrew/homebrew/blob/master/share/doc/h...

Fantastic! Then why is this an issue?

Re: El Capitan and Homebrew

#219
post #205

Earlier quoted context omitted.

> it should follow common unix standards Isn't /usr/local? > or at least fit in with OSX It did - before now /usr/local was available unprivileged with ownership. > rather than require a hack It only needs that now, since requirements to "fit in with OSX" have changed. That's not Homebrew's fault - they need a fast solution. Kudos in my book for responding before it's a problem.

No, /usr/local is normally 755 root:root (or whatever the effective equivalent is). Homebrew wants it to be 775 root:admin, so that users with the admin bit can write to it. That's not standard. People keep writing here as if El Cap removes /usr/local entirely. It does not. /usr/local is there by default. You only have to go into recovery mode if you've somehow removed it yourself.

> Homebrew wants it to be 775 root:admin

It's worse than that. Homebrew wants 775 $(whoami):admin.

Re: El Capitan and Homebrew

#220
post #18

How to disable SIP altogether: http://arstechnica.com/apple/2015/09/os-x-10-11-el-capitan-t...

Much like 'goto' statements in code, unless you really have a good reason to do you shouldn't disable SIP.
Post reply on HN