Live data from Hacker News

Homebrew 3.0

brew.sh

171–180 of 516 posts

Re: Homebrew 3.0

#171
post #130

Earlier quoted context omitted.

Contrarian view here: brew fucking sucks. It’s the worst package manager I’ve used for doing random unwanted updates at odd times. Someone else would have filled the void if homebrew hadn’t shown up, and it would hopefully have been better. I hate that brew is good enough that it’s got some kind of local maximum such that there’s no replacement forthcoming. There, I said it.

What do you mean by random unwanted updates? As far as I know, the only way to update is by running brew upgrade.

I ran `brew install graphviz` today and caught it running an upgrade of zeromq

Re: Homebrew 3.0

#172
post #128
post #21

Been a MacPorts user for years and I know nothing about Homebrew. To those who tried both: should a software engineer switch to Homebrew? MacPorts has its own way of dealing with dev tools and framework versioning. E.g. you can have multiple versions of complex products like PHP or MySQL at once. You can even have a GCC package for a specific target arch as a separate ports package. Does Homebrew allow these things?

MacPorts and Homebrew have a different philosophy of software installation. MacPorts wants to have its own thing over in /opt where it has its own toolchain independent from the system tool chain. This means that all users on the system share the same MacPorts software. This has an additional impact that it means that it requires privilege to install software there. Homebrew, on the other hand, uses the system toolch…

Given the moving nature of the OSX toolchain and directory structure, having your third party package manager integrated into the system toolchain increasingly feels like a bad idea.

Re: Homebrew 3.0

#173

Earlier quoted context omitted.

I feel like it would be a /tremendous/ amount of work to install packages -- which often have dependencies -- asynchronously. When is this really a problem, anyway? You should probably not have something like 'brew update' scheduled to run periodically, as then a broken package could break something unexpectedly. It should really only be run when you're ready to check for broken things, which means you can also sched…

Homebrew now runs `brew update` before every `brew install`, no? That's how it gets in the way, you just wanted to install a thing, and now you are stuck waiting for `brew update` -- which I feel takes longer than it used to? (You also may be confused between `brew update` and `brew upgrade`. I know I often am!)

Then `HOMEBREW_NO_AUTO_UPDATE` is probably for you.

> If set, do not automatically update before running brew install, brew upgrade or brew tap.

Re: Homebrew 3.0

#174
post #142
post #130

Earlier quoted context omitted.

What do you mean by random unwanted updates? As far as I know, the only way to update is by running brew upgrade.

Personally; only issue i tend to have is that when I install X, it breaks Y forcing reinstallation of ~everything. What should be a small install ends up taking 30m of cleanup. Entirely likely it's user error on my part; but also problem I haven't really had with other 'nix package managers.

[deleted]

Re: Homebrew 3.0

#175
post #3

I can’t even begin to imagine how much value Max Howell (creator of Homebrew) has added to the world. It’s the recommended package manager at every place I’ve worked at and saves so much headache. I use Linux at home and package managers like AUR are great, but macOS is where the users are.

Contrarian view here: brew fucking sucks. It’s the worst package manager I’ve used for doing random unwanted updates at odd times. Someone else would have filled the void if homebrew hadn’t shown up, and it would hopefully have been better. I hate that brew is good enough that it’s got some kind of local maximum such that there’s no replacement forthcoming. There, I said it.

If you've used Valet, you know truly that Brew is the worst.

Re: Homebrew 3.0

#176
post #130

Earlier quoted context omitted.

What do you mean by random unwanted updates? As far as I know, the only way to update is by running brew upgrade.

one time i ran “brew upgrade ffmpeg” which somehow forced a major version bump of postgres.

[deleted]

Re: Homebrew 3.0

#178
post #91

As a long-time Python user, Homebrew jumping versions from 2.7.0 to 3.0 is a little disorienting. :}

I'm waiting for comments like this one ahahaha. Can't agree more Iz datz some conspiracy?

Re: Homebrew 3.0

#179
post #130

Earlier quoted context omitted.

Contrarian view here: brew fucking sucks. It’s the worst package manager I’ve used for doing random unwanted updates at odd times. Someone else would have filled the void if homebrew hadn’t shown up, and it would hopefully have been better. I hate that brew is good enough that it’s got some kind of local maximum such that there’s no replacement forthcoming. There, I said it.

What do you mean by random unwanted updates? As far as I know, the only way to update is by running brew upgrade.

For some time now, in the default configuration, `brew upgrade` is run automatically any time you run `brew install`. You have to set HOMEBREW_NO_AUTO_UPDATE to disable this behavior.

EDIT: whoops, that was incorrect. It's actually `brew update` that is run automatically, which updates Homebrew itself plus all of its formulae. However, I think often the effect can't be similar. If formulae are updated, and the new package you're trying to install shares a dependency with other packages, the dependency will be automatically updated as part of the install process. I'm not sure if this can also trigger an update of an existing leaf package though.

Re: Homebrew 3.0

#180
I'm not familiar with Homebrew.

Is it the kind of thing I could use to manage packages in my own directory as a non-root user (on Linux)?

If so, will it be able to base itself on what my distribution offers, or will it build things up from scratch with its own toolchain packages?

Post reply on HN