141–150 of 255 posts
There has been a lot of talk in HN comments recently about Homebrew installing to `/usr/local`. With macOS Sierra, the user can no longer write to this folder without specifically owning it. Is there a security risk here and if so, whats the best workaround?
I've always installed to ~/.homebrew, and never encountered any problems.
Earlier quoted context omitted.
Well, he's at Apple now in charge of the Swift Package Manager, so I think he did okay.
He left.
Why does Homebrew need to parse Mach-O files? Is this for fixing up shared library paths inside executables?
Earlier quoted context omitted.
It's for this very reason that I'm still one of those old-school guys who still uses MacPorts. I was horrified to see this, and in my brief time using it, it actually caused me real problems, so I went back.
I almost went the other way (from ports to brew) because of the complex manual procedure required to fix ports when you upgrade the OS: https://trac.macports.org/wiki/Migration After going through the migration, it isn't that bad, but it was surprising (horrifying?) to me that ports was completely broken after an OS upgrade.
Earlier quoted context omitted.
Why? By which I mean that apt is fantastic AFAICT and totally integrated into Ubuntu and Debian. Why would you want a third party package manager?
The apt user experience is terrible compared with brew.
The interface seems more or less identical to me.
I'm not going to deny it's good and brings great stuff to the Mac, I'm just not seeing the advantages.
Earlier quoted context omitted.
It's for this very reason that I'm still one of those old-school guys who still uses MacPorts. I was horrified to see this, and in my brief time using it, it actually caused me real problems, so I went back.
I switched to MacPorts following the Google Analytics debacle [1] and how it was handled [2]. I had this expectation that MacPorts would be backwards and full of ancient packages but it's not - it's fantastic! The package repository is really good, the project itself is stable and it doesn't have a default-on analytics component aggregating my package data at Google. [1] https://news.ycombinator.com/item?id=11566720…
Be aware of "update bug" If Homebrew was updated on Aug 10-11th 2016 and brew update always says "Already up-to-date". you need to run: ``` cd "$(brew --repo)" && git fetch && git reset --hard origin/master && brew update ``` I had to.
I also had to do this. Keep in mind that ```brew update``` might take a while to output anything when you do this (it did for me), and then it will ask you to wait while it migrates to a new directory.
brew update brew --version
I've worked with mike to maintain formula for years and he is always pleasant and on top of things in what is a very hectic job. Homebrew is such a good package manager (and not for the reasons any package manager is classically considered good). It's great because the community is so vibrant, the user experience is so well thought out, and the formula dsl makes so much logical sense. It's actually both a GitHub and…
I've worked with mike to maintain formula for years and he is always pleasant and on top of things in what is a very hectic job. Homebrew is such a good package manager (and not for the reasons any package manager is classically considered good). It's great because the community is so vibrant, the user experience is so well thought out, and the formula dsl makes so much logical sense. It's actually both a GitHub and…
You can say that again. Homebrew's dependency management is a fucking joke, to the point that it might as well not exist.