Reminder that nothing in Homebrew has any signing or attempt at supply chain integrity. Now that they are moving away from clients using git, so even git commit signing is off the table now. When you install brew you are giving hundreds of people (or anyone who has access to their Github accounts) full remote code execution on your machine. Never ever use brew on a machine you use to access production.
I've been using Linux for the past 18 years or so, but damn do the M1 macs look interesting. How does one manage packages on a mac?
Homebrew 4.0.0
101–110 of 403 posts
Re: Homebrew 4.0.0
#102As an old hand who was around when homebrew started, I feel obliged to let people know there are alternatives. If you find brew's take-over-your-system-and-youll-thank-me approach off putting, and/or you value stability over the coolness factor, MacPorts is still alive and well ( https://www.macports.org ), and in-fact has basically all the same packages brew does. In 18 years of using MacPorts, it's never messed up…
Re: Homebrew 4.0.0
#103On macOS, has anyone moved from/to MacPorts to/from Homebrew? Why did you move? What are the pros and cons of each system?
Moved from homebrew to nix. Haven't looked back. If something is not on nix, I just build/compile it myself.
https://pkgsrc.joyent.com/install-on-macos/
Anything that nix does better than pkgsrc?
Re: Homebrew 4.0.0
#104As an old hand who was around when homebrew started, I feel obliged to let people know there are alternatives. If you find brew's take-over-your-system-and-youll-thank-me approach off putting, and/or you value stability over the coolness factor, MacPorts is still alive and well ( https://www.macports.org ), and in-fact has basically all the same packages brew does. In 18 years of using MacPorts, it's never messed up…
And, as a counter to your experience of not having it mess up a machine, every time you upgrade macOS to the next major version you have to jump through some hoops to get it to play ball again. Painful.
At some point I gave up on the hoops and installed homebrew instead and haven't looked back.
Re: Homebrew 4.0.0
#105Earlier quoted context omitted.
Moved from homebrew to nix. Haven't looked back. If something is not on nix, I just build/compile it myself.
I use pkgsrc, which also comes with binary packages through pkgin, although I rarely need to compile things myself. https://pkgsrc.joyent.com/install-on-macos/ Anything that nix does better than pkgsrc?
Re: Homebrew 4.0.0
#106I despise, despise, Homebrew's "we know better than you" approach to always installing the latest versions of every dependency. How tf is this fine? They don't even offer alternative. They just say "we can't test all of the packages installed and all version combinations, so this is the best we can do". Well, no one asked you to test my exact setup. All I'm asking for is: if I have perfectly working Node 18 and I nee…
Re: Homebrew 4.0.0
#107While I use Homebrew on my Mac — it is a major risk. I am afraid that the project is not following strict security policies and will be compromised at some point. Evil package or evil version of brew can steal or modify my data. I think this will also hurt the Mac platform. I wish Apple would invest some effort into building an App Store for cli programs. While it may be complicated for the community(require signing,…
Re: Homebrew 4.0.0
#108Re: Homebrew 4.0.0
#109Earlier quoted context omitted.
None of this is user-friendly - all of it is obfuscated. I have to add resources to my system (env vars) in order to opt-out - and that is the issue! There are no hints/tips about this produced to educate a new user - if it weren't for your help, I wouldn't have known. The non-resource-using method I propose is that homebrew merely ask the user if its okay, after 5 or 10 runs, to send some info - and then shows me th…
> None of this is user-friendly - all of it is obfuscated This is a message which is printed with very clear instructions the first time you run any command. It’s a simple command and there’s no noticeable difference in resource usage compared to the actual package management system, which also needs environmental variables to be set. The big thing you’re missing is that the Homebrew maintainers are freely giving you…
I've donated to homebrew, I support them that way.
The moral issue is, I'm using their tools and trusting them, and they are violating that trust by phoning home and sending analytic data without my involvement or approval. While it may seem trivial to you to set an environment variable, having to do that with every new homebrew install adds up, and when its forgotten about, results in a negative impact on my networking and IT resources.
> a trivial opt-out mechanism
Its not trivial, and thats the point where we disagree. No, maintaining environment variables to prevent tooling from sending unknown analytical data: this is not trivial. It is an anti-pattern designed to gain the data from un-sophisticated users, rather than treating users with respect and letting them have agency over whether their resources are used by the homebrew developers.
Tracking should always be opt-in and if it isn't, that is simply a dark pattern being used to scam resources from the users.
Re: Homebrew 4.0.0
#110> brew update will now be run automatically less often (every 24 hours rather than every 5 minutes) and these auto-updates will be much faster as they no longer need to perform the slow git fetch of the huge homebrew/core and homebrew/cask taps’ Git repositories. Excellent! Thanks to the brew team for this — it was always frustrating to install something and have to wait for a full, slow update first.