291–298 of 298 posts
Earlier quoted context omitted.
OS X has always provided a fine Unix experience for me.
If you're OK with Apple taking away root privileges on your box, then I guess a lot of things that are fine with you are not going to be fine with other people. Enjoy using Apple's computers...and they are Apple's, not yours because if they were, you'd be in control.
Earlier quoted context omitted.
Those fixes applicable to Yosemite will be available as a separate Security Update. Apple usually supports the current OS and the OS X version behind (for example, this for Mavericks was released in August: https://support.apple.com/kb/DL1834?viewlocale=en_US&locale=... ). So security is probably not a reason to upgrade.
Are they back porting rootless?
Users should have full control over their own machines. System Integrity Protection is obnoxious paternalism at best, and at worst, it's just another step toward iOS-ification. If Apple keeps this up, I expect a revival of Linux desktop distributions.
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.
Earlier quoted context omitted.
Dishonest marketing? Really? Homebrew, a free tool was out spreading lies about MacPorts? That's ridiculous. When pretty much every major Ruby shop uses Homebrew, why would I want to kick around with MacPorts? I trust Thoughtbot, Pivotal, etc, far more than the two guys actually using MacPorts. Perhaps Homebrew 'won' in that particular community because it was better, ever considered that? Wide community adoption is…
> Dishonest marketing? Really? Homebrew, a free tool was out spreading lies about MacPorts? That's ridiculous. Ridiculous? Homebrew's marketing tagline was "MacPorts driving you to drink? Try homebrew!". The (obviously uninformed) slams of MacPorts and Fink didn't stop there. It was the first time I'd ever seen negative marketing against a competing OSS project. > When pretty much every major Ruby shop uses Homebrew,…
Perhaps you never didn't use macports or fink a few years back?
They were terrible.
Perhaps, now, they're slightly better, but there was a time about oh... 2 years ago, when macports specifically actually made me want to punch my computer.
I can't speak for anyone else, but I can say, that for me, personally, every complaint leveled against them was absolutely spot on.
Earlier quoted context omitted.
If you're OK with Apple taking away root privileges on your box, then I guess a lot of things that are fine with you are not going to be fine with other people. Enjoy using Apple's computers...and they are Apple's, not yours because if they were, you'd be in control.
Feel free to disable sip, or just unprotect the folders you don't want protected (although the latter would get wiped out after updates).
Read this:
http://lexsheehan.blogspot.com/2015/10/el-capitan-homebrew-a...
Earlier quoted context omitted.
Ditto. And Homebrew's policy of avoiding installation of built-in packages by default means that you don't accidentally break your whole system when MacPorts shadows a critical core package.
I can't fathom how MacPorts could ever break your whole system. - MacPorts' /opt/local is not in any of the default system paths. - MacPorts uses sandboxing to ensure that builds can't stomp anything outside of /opt/local
edit
should be noted you really ought not do this and if you absolutely have to you should use DYLD_FALLBACK_LIBRARY_PATH