Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Upgrading Homebrew and avoiding the "failed to verify attestation" error

til.simonwillison.net

Post reply on HN
Print view View original

31–40 of 46 posts

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#31

Post by zombot »

JTyQZSnP3cQGa8B wrote: post #3
cglan wrote: post #2

I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far

MacPorts is a great alternative, also way older but never has been as successful as Homebrew.

Homebrew is really the worst of all the options on macOS, I wonder how it became so popular in the first place.

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#33

Post by lloeki »

ashconnor wrote: post #27
mootoday wrote: post #8

All I can say when I see Homebrew: "I replaced Homebrew with Devbox" [1] [1] https://mootoday.com/blog/i-replaced-homebrew-with-devbox

Some folks are running nix on OSX along with nix-darwin. https://github.com/LnL7/nix-darwin

nix-darwin is the cherry on the cake, plain nixpkgs is already miles better than homebrew.

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#34

Post by iforgotmysocks »

ryandrake wrote: post #10
vbezhenar wrote: post #7

Earlier quoted context omitted.

My issues with homebrew are: 1. I hate the concept of dependency management. I want every package to ship with all dependencies inside. Just download tarball, extract and that's about it. 2. homebrew often wants to install things I already have, like python. 3. No easy way to install old packages. I don't understand why things are made harder than they should be.

Dependencies are totally out of control, in much of OSS, not just Homebrew. I probably have 5-6 leaf node packages that I actually installed with brew install, but brew list shows close to 100 little dependencies. Same with apt on my Ubuntu/Debian systems. I physically installed a handful of applications but my system has hundreds of packages installed. At least it’s not DLL Hell: the dependency management tools are…

You might be able to a nice graph with this command: brew deps --installed --graph

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#35

Post by [deleted] »

gkoller wrote: post #25
zdw wrote: post #4

Earlier quoted context omitted.

Second recommendation for MacPorts It predates Homebrew by a bit and is under Apple's http://www.macosforge.org umbrella of OSS projects, so as close to 1st party support as you can get.

MacPorts rocks. No ports breaking when upgrading MacOS as can (or could,not sure if that's still an issue) with Brew.

[deleted]

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#36

Post by iforgotmysocks »

zdw wrote: post #4
JTyQZSnP3cQGa8B wrote: post #3

Earlier quoted context omitted.

MacPorts is a great alternative, also way older but never has been as successful as Homebrew.

Second recommendation for MacPorts It predates Homebrew by a bit and is under Apple's http://www.macosforge.org umbrella of OSS projects, so as close to 1st party support as you can get.

It seems like Apple also closely work with Homebrew - https://news.ycombinator.com/item?id=41708046#41711168

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#37

Post by stavros »

vbezhenar wrote: post #21
valbaca wrote: post #14

Earlier quoted context omitted.

> I want every package to ship with all dependencies inside. Stopping where? python? c libraries? glibc? the kernel? "all the dependencies" isn't what you think it is > 2. homebrew often wants to install things I already have, like python. oh yeah "python" like it's just A Thing You have. nothing has versions and of course every version can execute every code that's ever been written, past and future. > I don't under…

> Stopping where? Where OS provides guarantees. If OS provides guarantee that libc will be there, do not ship libc. If OS provides guarantees that python will be there, do not ship python. If you do ship python, hide it very well, so I'd never even know about it, unless I go out of my way. And it'll never be shared by anything. Those questions are easy and solved by every commercial software. They need to make those…

I'm sure you're familiar with versions. What happens when your software depends on a libc that has a function that was removed on the newer version, or added since the previous one? Now older or newer versions of libc don't work with your software, even though they're "there".

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#38

Post by drcongo »

vbezhenar wrote: post #7
cglan wrote: post #2

I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far

My issues with homebrew are: 1. I hate the concept of dependency management. I want every package to ship with all dependencies inside. Just download tarball, extract and that's about it. 2. homebrew often wants to install things I already have, like python. 3. No easy way to install old packages. I don't understand why things are made harder than they should be.

My biggest gripe: You can only have one homebrew user per machine, so on a multi-user, multi-admin Mac, only one of those is allowed to brew install.

Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error

#39

Post by boffinAudio »

vbezhenar wrote: post #7
cglan wrote: post #2

I’ve switched over to devbox, which is a thin, easy to use wrapper around Nix on osx. Haven’t had to install brew yet. Brew was simple in theory but I always ran into so many issues like this, or just various packages polluting everything. Fingers crossed I don’t have to go back As someone who hates tinkering with this kinda stuff, I’m surprised how well it works so far

My issues with homebrew are: 1. I hate the concept of dependency management. I want every package to ship with all dependencies inside. Just download tarball, extract and that's about it. 2. homebrew often wants to install things I already have, like python. 3. No easy way to install old packages. I don't understand why things are made harder than they should be.

>2. homebrew often wants to install things I already have, like python.

I think its important to understand why this is the case. The python you think you have already, out of the box in MacOS, is the system python. Its not the python you should be using - its the one that python-based tools that your system depends on, is using.

Brew installs other versions of python - and gives you access to tools that allow you to maintain completely independent, different versions of python - for a very good reason.

You simply should not be using the system python for tools that are outside the purview of the system tools - doing so can lead to broken essential system tools.

So, don't be so quick to resist this aspect of package management. Its also true of Linux, by the way - developers should be using their own python installations, and not just glomming libraries into the system-provided python tree .. to do so, is to live very dangerously as a systems operator and as well as a developer.

Post reply on HN