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

Show HN: Homebrew 6.0.0

brew.sh

Post reply on HN
Print view View original

241–250 of 380 posts

Re: Show HN: Homebrew 6.0.0

#241

Post by [deleted] »

mikemcquaid wrote: post #58
0xbadcafebee wrote: post #13

Personally I stopped using Homebrew after I got screwed too many times on mandatory upgrades that I couldn't pin. I use a combination of Mise and MacPorts now so I don't get any more surprise breakage and forced obsolescence. Plus Mise allows me to upgrade to any new version, whereas with Homebrew you have to wait for whenever the tap feels like upgrading (llama.cpp tap skips every 10 releases)

Glad you've found a workflow that works for you, genuinely. For others still using Homebrew: a lot of work has gone into upgrading only when we absolutely have to and showing these upgrades to the user before we do them, including in this release.

[deleted]

Re: Show HN: Homebrew 6.0.0

#242

Post by cavneb »

mikemcquaid wrote: post #29
hk__2 wrote: post #24

Hi Mike, I’m @bfontaine on GitHub (I helped maintain Homebrew in ~2014-2016). I’m always impressed at your longevity as a maintainer; it’s been like what, 16+ years you’ve been maintaining Homebrew and you’re still here, still shipping new features! Thank you for everything!

17 in September. Thanks for all your great work at the time! Hope you’re well <3

Thank you Mike!

Re: Show HN: Homebrew 6.0.0

#243

Post by analog_daddy »

jamesgill wrote: post #63

I know this runs on Linux too. As a Linux user, I'm unclear on why I might use this instead of apt or dnf, for example. Any Linux users out there have experience with both Homebrew and one of these?

Yes. I daily drive pop os now. Hate to use flatpak for anything. Only install core packages, google chrome and vscode using apt. Almost everything else is installed using homebrew. The idea is have a base stable system for UI and basic shell. Usually get the latest packages from brew. Earlier same base system but had distrobox with arch toolbox. Planning on using this scheme going forward, especially since while I love rolling release, they sometimes might have regressions which I don’t want to deal with right away. And these regressions can be both at system level or user packages level. Having a stable base helps significantly in daily driving linux in real world.

Re: Show HN: Homebrew 6.0.0

#244

Post by [deleted] »

jrmg wrote: post #105
asdff wrote: post #74

Earlier quoted context omitted.

Maybe among the general mac population they are a rounding error. But among the mac population who actually peeks behind the curtain and uses homebrew?

Maybe I’m just biased because it’s what I’ve done personally, but almost everyone using an old Intel Mac as a server is surely running Linux?

[deleted]

Re: Show HN: Homebrew 6.0.0

#245

Post by analog_daddy »

latexr wrote: post #94
jamesgill wrote: post #63

I know this runs on Linux too. As a Linux user, I'm unclear on why I might use this instead of apt or dnf, for example. Any Linux users out there have experience with both Homebrew and one of these?

You can run Homebrew on Linux without admin privileges. Useful e.g. for shared hosting.

Small note: You need admin privileges only once for the first install which creates a new user `linuxbrew` and everything is based around `/home/linuxbrew` prefix. The issue is on systems where getting an admin access is not possible, you cannot ‘reliably’ install to a different prefix. It is currently unsupported.

Honestly, I would settle for a custom prefix if it tells me exactly what packages will break and what won’t without having to read each and every formula recipe. That’s one thing that bothered me for a while and I did not have the willpower to explore that direction without having community support.

Re: Show HN: Homebrew 6.0.0

#246

Post by lkbm »

phplovesong wrote: post #56

Does homebrew still do that insane thing when you want to upgrade a single package it tell you "hold my beer" and starts installing postgres and some obscure python version?

Are you referring how it does a `brew upgrade` when doing a `brew install`? It should tell you how to disable that whenever it happens:

> Adjust how often this is run with `$HOMEBREW_AUTO_UPDATE_SECS` or disable with

> `$HOMEBREW_NO_AUTO_UPDATE=1`. Hide these hints with `$HOMEBREW_NO_ENV_HINTS=1` (see `man brew`).

Re: Show HN: Homebrew 6.0.0

#247

Post by golem14 »

golem14 wrote: post #203
m0do1 wrote: post #112

Earlier quoted context omitted.

there is `brew update`

sure, but is that doing the same as deleting all installed sw and then reinstalling it using the new safeguards? Assuming I have already installed something homebrew 6 would not let install, will I get a warning?

I tried brew upgrade on my setup, got a bunch of warnings about untrusted taps, and it upgraded what it could, and updated itself to homebrew 6.0.0. So I guess, yay ?

Re: Show HN: Homebrew 6.0.0

#248

Post by yreg »

mrpippy wrote: post #104
philistine wrote: post #53

The deprecation of Intel support is agressive! Every Mac enthusiast I know who uses a Mac as a server uses their old machines, which are pretty much all Intel. We'll lose support from you guys a year before Apple! I know supporting Intel is an ordeal and a choice, but I'm firmly on the camp that Homebrew should find a way to maintain Intel support as long as possible.

At this point that would be a 2018 Mac mini, which can only run Sequoia (which will be out-of-support at the same time as Homebrew drops Intel support). If you want Intel support, MacPorts still runs back to Leopard.

And all 27" iMacs.

Re: Show HN: Homebrew 6.0.0

#249

Post by c-hendricks »

srcrip wrote: post #221
PufPufPuf wrote: post #57

Earlier quoted context omitted.

Here's my modest collection of global tools I install in my dotfiles: https://github.com/JanPokorny/dotfiles/blob/master/dot_confi... Projects then have their own dependencies, e.g. https://github.com/i-am-bee/agentstack/blob/main/mise.toml Mise also has a task runner which automatically uses correct tools. Onboarding a new team member is super easy now, they just need Mise, "mise install" and they're up.

How does this even work? How does mise know how to install these things?

Mise has many backends. A lot comes from Aqua / asdf, but there's others like GitHub, npm, cargo, http, etc.

It's all fairly well documented here: https://mise.jdx.dev/dev-tools/backends/

Post reply on HN