Upgrading Homebrew and avoiding the "failed to verify attestation" error
41–46 of 46 posts
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#42I’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
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#43Earlier quoted context omitted.
> 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
#44I’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.
Well macOS does ship with Python but it's a true pain in the rear to deal with version conflicts of global packages.
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#45Earlier quoted context omitted.
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…
But it's nice to reuse code
It doesn't mean we can't run it twice.
Re: Upgrading Homebrew and avoiding the "failed to verify attestation" error
#46Earlier 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.
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.
I have had a small amount of success installing in home, when I had a locked down machine for work but it really wants to fight it.