I wonder how many more major versions until "brew update" and "brew upgrade" finally just do the same thing. "But they're not the same!" I don't care.
> I don't care.
It doesn't change facts.
151–160 of 403 posts
I wonder how many more major versions until "brew update" and "brew upgrade" finally just do the same thing. "But they're not the same!" I don't care.
> I don't care.
It doesn't change facts.
Earlier quoted context omitted.
FWIW, Homebrew uses /opt/homebrew instead of /usr/local on Apple Silicon installations, as far as I know that was the main sticking point for the complaint that it took over your system. Still isn’t terribly useful for multi-user systems as far as I know, but for my personal laptop this will never be a problem that I have to deal with. I used pkgsrc on macOS for a while but ended up going back to Homebrew because it…
> I haven’t used Macports so couldn’t compare - can Macports install .app applications? Yes, I have Emacs installed via MacPorts for example.
Earlier quoted context omitted.
Using SQLite instead of JSON could have worked too and would likely make the manifests smaller: > curl -sI https://formulae.brew.sh/api/formula.json | grep content-length => 19898457 (~19.9MB) > curl -sI https://formulae.brew.sh/api/cask.json | grep content-length => 4023930 (~4MB) But the JSON API has been around for a while so brew 4.0 just makes use of it by default. Brew 3.3 added an off-by-default HOMEBREW_INSTA…
Homebrew actually passes `--compressed` here so it's smaller: > curl -sI --compressed https://formulae.brew.sh/api/formula.json | grep content-length => 3482583 (~3.3MB) > curl -sI --compressed https://formulae.brew.sh/api/cask.json | grep content-length => 722915 (~0.6MB)
Earlier quoted context omitted.
But do I need the latest openSSL for local development? Seems more trouble than it should.
That’s why they keep it private by default, but the answer is often yes. There have been multiple times where a package like Python 3.10 required a newer version (1.1.1) than the OS release included (I suspect that’s also why the AWS Lambda runtime is stuck on 3.9 since it’s based on Amazon Linux 2 and that uses 1 .0). This has settled down a bit but the big HTTPS-everywhere push last decade flushed out a ton of thin…
I 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…
You could always manage your packages and their dependencies yourself. Or you could release a new package manager which does provide support for that functionality, build out a team of maintainers, and stay on top of all the releases
So according to you nobody is allowed to criticise anything because “shut up and build it yourself if you dont like it”?
Earlier quoted context omitted.
Yes, I know, but most Unix things on my Mac are either installed by homebrew or myself, so I think it’s safe. But it’s a desperation act for sure. Why do you say it’s wrong on Apple Silicon? If you mean system integrity protection stuff, I don’t think it applies to /usr/local
> Yes, I know But other users might not, and you wrote that as a reply to someone asking how to do it. My comment was meant to warn others they should not go that route, especially when there’s an official uninstallation script (linked in my other comment). > Why do you say it’s wrong on Apple Silicon? Because in that case Homebrew installs to /opt/homebrew, not /usr/local.
Earlier quoted context omitted.
> Why does a package manager need to track their users at all? According to https://docs.brew.sh/Analytics they use it to measure how often formulas fail to install, to get overall metrics on which OS versions are used, and to correlate those (i.e. to tell on which OS versions specific packages fail to install correctly). > A maintainer has no need to know who's installing what Aside from the IP, they don't know who'…
All stuff that should be in a trouble ticket from a whiney user. Which we know this type of user would be. Edit-Also, this is for Mac OS. Chose a few standard OSes to support and test them. If a system update will fix the issue then it shouldn't be fixed at the package manager level.