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

361–370 of 380 posts

Re: Show HN: Homebrew 6.0.0

#361

Post by notpushkin »

FireInsight wrote: post #346
notpushkin wrote: post #125

Earlier quoted context omitted.

Hmm, `mise use -g docker-cli` works for me. `docker compose` is a bit trickier – it gets installed as `docker-cli-plugin-docker-compose`, but docker-cli doesn’t seem to pick it up. I’ve added a symlink as `docker-compose` for the time being. Also using brew for casks, and I think there’s a couple tools I couldn’t install with mise (e.g. pngpaste and zbar for scanning QR codes from screenshots).

There's the rename-exe option in mise.toml to rename the docker compose binary to `docker-compose`. I've used it on some machine, I think. Look it up in the docs, it doesn't take long to wire up.

Yep, I’ve ended up doing exactly that: https://news.ycombinator.com/item?id=48501953

The default docker-compose definition comes from aqua:docker/compose though, which does not support rename_exe. You have to specify github:docker/compose instead.

Re: Show HN: Homebrew 6.0.0

#362

Post by thewhitetulip »

matsemann wrote: post #327
latexr wrote: post #320

Earlier quoted context omitted.

The whole concept comes from homebrewing. https://en.wikipedia.org/wiki/Homebrewing

Yeah, I guess it's not being a native English speaker, so one just accept most of the words almost as names without thinking about any other meaning the word might have.

For me it was just a command lol

It's now that I am reflecting back that it's all related to home brewing!

Re: Show HN: Homebrew 6.0.0

#363

Post by Milpotel »

shakna wrote: post #298
Milpotel wrote: post #287

Earlier quoted context omitted.

> It’s not horribly broken any more than your toaster is for not needing constant updates. I don't know where this sense of "stable" in the community comes from. Software isn't perfect and gets fixed all the time. Yes, there are packages with different maintained stable branches that you can pin for your LTS distribution but this is by far the minority. For the other stuff you constantly have to work around missing f…

The "outdated" package, probably has all these security fixes [0]. That's why it exists - to maintain something safely. You step back from latest and greatest, to not get a compromised system the next time something goes wrong. [0] https://sources.debian.org/patches/jq/1.7.1-6+deb13u2/

Nope, it hasn't because developers fix bugs along the way without notifying package maintainers.

Re: Show HN: Homebrew 6.0.0

#364

Post by bbkane »

ryandrake wrote: post #73
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)

I've moved over to MacPorts due to Homebrew's aggressive support phase-out schedule[1]. My daily driver iMac is now in the Tier-3 "go away" bucket. Absolutely loved Homebrew for the short period of time I could use it, but I'm not going to get on the hardware update treadmill just to keep using it. 1: https://docs.brew.sh/Support-Tiers

I think you should blame Apple rather than Homebrew for this. Apple, please support your hardware longer!

Re: Show HN: Homebrew 6.0.0

#365

Post by jdxcode »

notpushkin wrote: post #361
FireInsight wrote: post #346

Earlier quoted context omitted.

There's the rename-exe option in mise.toml to rename the docker compose binary to `docker-compose`. I've used it on some machine, I think. Look it up in the docs, it doesn't take long to wire up.

Yep, I’ve ended up doing exactly that: https://news.ycombinator.com/item?id=48501953 The default docker-compose definition comes from aqua:docker/compose though, which does not support rename_exe. You have to specify github:docker/compose instead.

doesn't aqua:docker/compose just work? it does for me

Re: Show HN: Homebrew 6.0.0

#366

Post by notpushkin »

jdxcode wrote: post #365
notpushkin wrote: post #361

Earlier quoted context omitted.

Yep, I’ve ended up doing exactly that: https://news.ycombinator.com/item?id=48501953 The default docker-compose definition comes from aqua:docker/compose though, which does not support rename_exe. You have to specify github:docker/compose instead.

doesn't aqua:docker/compose just work? it does for me

Nope :-( Just tried it again, it installs and is available in PATH as `docker-cli-plugin-docker-compose`, but `docker compose` says “unknown command”. For docker-cli to pick it up, it should be in $DOCKER_CONFIG/cli-plugins/docker-compose (~/.docker by default, though I use ~/.config/docker).

rename_exe doesn’t do anything on the aqua backend either (and isn’t a documented option). I’m on mise 2026.5.10 right now though so if you fixed something recently I might be missing out!

Re: Show HN: Homebrew 6.0.0

#367

Post by cbeach »

cbeach wrote: post #323
sgt wrote: post #299

Earlier quoted context omitted.

I've heard of that but never experienced it on my Google. Weird. I just retried that now and it's giving the correct link. Maybe that's why it's not being fixed.

I reported the ad to Google immediately, and when I checked back an hour later the search results were clear. But I suspect it's only a matter of time before another one slips through the net. I think what happens is a legitimate business with a history of legit Google advertising gets compromised by malware, and then their Google adverts are flipped.

Just heard back from Google regarding my report of the ad that served malware to me:

> Dear Chris,

> We’re writing to let you know that we reviewed your report (ID 579240969280369002).

> Here's what we found

> We decided not to take this ad down. We found that the ad doesn’t go against Google’s policies, which prohibit certain content and practices that we believe to be harmful to users and the overall online ecosystem.

I think the safest thing I can do right now is avoid using Google for searches and instead use Claude, which at least has functioning safeguards, and is less easily poisoned than Google Search.

Re: Show HN: Homebrew 6.0.0

#368

Post by theragra »

eikenberry wrote: post #161
theragra wrote: post #142

Earlier quoted context omitted.

Comparison of which managers? Adding package to homebrew is straightforward, except that it has a lot of (reasonable?) requirements to make it right. Basically, you make a PR with a "formula" to their main repo from your branch. Formulas are ruby programs. LLM can do it easily, and such code is accepted if correct.

Homebrew, mise, flox, devenv are the first ones I can think of.. Arch Linux's AURs get an honorary mention as they are used in the similar way on that distro and Arch + distrobox gets the same results. A quick search shows there are many others but it doesn't look like a comparison exists for this area and I'm getting OK results out of AI comparisons. I'll just dig into it that way.

I think homebrew is different in comparison to flox,mise and devenv. Later are for reproducible dev envs, former is for installing tools globally where you cannot/do not want traditional package managers or building from source.

Re: Show HN: Homebrew 6.0.0

#369

Post by shakna »

Milpotel wrote: post #363
shakna wrote: post #298

Earlier quoted context omitted.

The "outdated" package, probably has all these security fixes [0]. That's why it exists - to maintain something safely. You step back from latest and greatest, to not get a compromised system the next time something goes wrong. [0] https://sources.debian.org/patches/jq/1.7.1-6+deb13u2/

Nope, it hasn't because developers fix bugs along the way without notifying package maintainers.

You might need to expand on that. Considering the CVE patches that are on the link I just shared.

Re: Show HN: Homebrew 6.0.0

#370

Post by ryandrake »

bbkane wrote: post #364
ryandrake wrote: post #73

Earlier quoted context omitted.

I've moved over to MacPorts due to Homebrew's aggressive support phase-out schedule[1]. My daily driver iMac is now in the Tier-3 "go away" bucket. Absolutely loved Homebrew for the short period of time I could use it, but I'm not going to get on the hardware update treadmill just to keep using it. 1: https://docs.brew.sh/Support-Tiers

I think you should blame Apple rather than Homebrew for this. Apple, please support your hardware longer!

Apple doesn’t force Homebrew to model its support policy on Apple’s.
Post reply on HN