381–390 of 403 posts
Earlier quoted context omitted.
I believe you need to set the envvar HOMEBREW_NO_AUTO_UPDATE to avoid that problem.
I always encourage folks to read over the environment section of the manpage, as it's extremely helpful: https://docs.brew.sh/Manpage#environment
Earlier quoted context omitted.
Switched to MacPorts on an older machine which Homebrew dropped support for (and deleted all prebuilt binaries) While neither is great as a package manager, especiall with their dependency resolution, here are a few pros&cons: Apps: ++ Brew has a much more up-to-date collection, also more non-source binaries. App customization: + Port, Brew dropped support for custom install flags a while ago + Brew you can setup aut…
> Space: + Brew. Both waste it with their poor package repository architecture, but with Brew you can at least delete the repo after the first install and use their API to download updates. BTW, with this release the Homebrew uses the API by default and doesn't clone the repos unless necessary.
Earlier quoted context omitted.
By default, Homebrew requires world-writeable location in the PATH (doesn't matter if it's /opt/homebrew or /usr/local). In my opinion, this isn't a sensible choice. Homebrew, as the name implies, was built for hobbists with little regards for security. Not a problem for many, but it does make it incompatible with a corporate environment.
It does matter though? /opt/homebrew is specifically used by Homebrew, whereas /usr/local is kind of a more shared location that old Homebrew hijacked. Either way, I think bad default folders is better than bad default security practices. Most package manager forces you to use sudo to run them as root, and I think that's much much worse in terms of security practices and encourages the wrong behaviors and potentially…
Earlier quoted context omitted.
Does Nix still have that extremely steep and high learning curve and huge time invest before you actually grok it? I'd love a Nix that is about as hard to use as homebrew, but no luck so far.
Imo, no. I think the documentation is very good, unlike what I had heard. The thing that I really had to invest in was my ability to patiently read documentation closely instead of aimlessly trying to find a shortcut by jumping around the doc pages.
Earlier quoted context omitted.
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
That's like saying "if you don't like your country, start your own". The goal isn't to abandon homebrew, but to have it not break things all the time.
Earlier quoted context omitted.
That’s not the point. I don’t want any software sending analytics unless I specifically allowed it.
I feel the same way. I think it’s not cool when orgs track telemetry with opt out. But it’s not cool like when you’re at a party and you go off and fart in the corner as no one’s there and then a few seconds later someone walks by and smells it. Continuing the analogy, telemetry with no opt out is like farting silently amongst a group of people. And tracking identified user requests while selling data is like slappin…
Earlier quoted context omitted.
I've been using Nix (and, occasionally, MacPorts) instead of Homebrew for a few years now. Works great, and doesn't have that particular issue. If Nix seems like a bridge too far, the Devenv project offers some nice, lightweight porcelain atop the raw Nix experience.
Does nix have pre-built binaries for m1/m2/arm macs? I'm not enjoying having to rebuild clang and gcc as build-deps with macports... :/
Earlier quoted context omitted.
I believe they used to do `--depth` but GitHub complained because their systems weren't optimized for that and it ended being cheaper for the servers to send you the whole thing (much easier to figure out what refs you needed, or something along those lines).
I don't know anything about how git servers are implemented, but this is super weird to me. Why couldn't you basically just copy the files (excluding .git), then do `git init`, set the upstream remote, and fetch only the most recent commit? I'm guessing it wouldn't work _exactly_ like that because the git cli is convoluted and nobody remembers the exact semantics of every flag, but it seems surprising that there aren…
Earlier quoted context omitted.
There's nothing wrong with the website though. Ugly is highly subjective
What are the odds that an Apple user finds that site attractive? I come from the linux world, so fine by me, but I'm no dummy, this site looks like it's going to tell me it runs better in a modern browser like IE6.
Earlier quoted context omitted.
It is not feasible to avoid installing any third-party software. Moreover I admitted that I use Homebrew. However I don’t understand what makes Homebrew reliable. Homebrew is a non-profit project run entirely by unpaid volunteers. I trust repositories controlled by corporations (RHEL, Ubuntu) or properly(?) governed non-profit organizations (Debian) more. Also I trust App Store more, because of sandboxing, static and…
I don't understand the distinction you're making between Homebrew and other non-profit OSS orgs: Homebrew has a documented governance structure[1] and is hosted under a non-profit foundation. The App Store exists primarily to distribute proprietary applications. Homebrew exists primarily to distribute open source packages. Comparing the two (and Apple's justified focus on sandboxing, etc.) feels like a mismatch. [1]:…