Live data from Hacker News

Homebrew 1.1.0

brew.sh

181–190 of 216 posts

Re: Homebrew 1.1.0

#181

Earlier quoted context omitted.

Agreed. Homebrew has saved countless hours for developers, I can't believe how many hours I used to spend installing/updating different versions for testing. Now we just run (>brew switch package version) done.

Whoaaa didn't know that command. This could replace something like say nvm?

I don't think so. In my experience brew only has a very limited selection of versions of packages, which is understandable.

Re: Homebrew 1.1.0

#183
post #113

Earlier quoted context omitted.

I haven't done a clean install of OS X in a long time, but I'm pretty sure /usr/local/bin exists. But even if it doesn't I don't find this a compelling argument. Having /usr/local/bin owned by root is a universally accepted standard in the unix world, and with very good reason: having /usr/local/bin owned by a user introduces security risks.

I believe /usr/local/bin is empty on a fresh install.

It should be -- after all, it's there for local software.

Re: Homebrew 1.1.0

#184
post #170

Earlier quoted context omitted.

Basically all of the unixy tools I need host-side (a lot of my work happens in Debian VM's or on remote Debian servers) are available as native Installer Packages (.pkg or .mpkg bundles) This boils down to: Vagrant, Mercurial, Git, GPG Suite, Autotools, tree and wget.

And for updates you manually hunt down the new .pkg installers? Package managers are not only there to install some version of the software, but also to keep it up-to-date.

Hunting implies I don't know where to find them and have to search.

Re: Homebrew 1.1.0

#185
post #19

Probably stupid question but: how do you update your version?

Try:

    $ brew update # get latest version of Homebrew
 
    $ brew cleanup # Homebrew housekeeping
 
    $ brew cask cleanup # Cask housekeeping
 
    $ brew --version
    #Expected output: Homebrew 1.1.0

Re: Homebrew 1.1.0

#186
post #178

Earlier quoted context omitted.

Nix package manager on my Mac [1]. Deterministic builds, plays well with POSIX/UNIX, though fewer repo's available than Brew and others. [1]: https://news.ycombinator.com/item?id=11772686

I tried switching to nix, but homebrew's command line argument "design" has spoiled me. With homebrew I'm usually able to guess command arguments, where as with every other package manager I have to google when I want to do something I haven't done before. For example, I want to search for a package name before installing. I'm guessing it's just "brew search pkg"... yup. Now what do I do with nix? Google says it's "n…

Haha, this is true, Nix's commandline is not exactly intuitive. I've been using apt, vim, and other similarly unintuitive stuff for a long time though so I just deal with it or script it, but totally understand anyone who prefers something more semantic.

Re: Homebrew 1.1.0

#187
To echo everyone else: Apple should be paying you folks a boat load of money. If homebrew didn't exist, I don't think we'd bother with macOS as a developer environment.

Re: Homebrew 1.1.0

#188
post #64

I have very mixed feelings about homebrew. When it works, it is awesome, but when it doesn't it can be a serious nightmare. In particular, homebrew refuses to run under sudo. Instead, to instal in /usr/local it wants me to recursively chown /usr/local to myself, which is a Really Bad Idea (tm). I have mostly stopped using it for this reason. I understand that running a program that runs third-party scripts under sudo…

Just install to a different folder. Everything still works.

Re: Homebrew 1.1.0

#189
post #64

I have very mixed feelings about homebrew. When it works, it is awesome, but when it doesn't it can be a serious nightmare. In particular, homebrew refuses to run under sudo. Instead, to instal in /usr/local it wants me to recursively chown /usr/local to myself, which is a Really Bad Idea (tm). I have mostly stopped using it for this reason. I understand that running a program that runs third-party scripts under sudo…

> recursively chown /usr/local to myself As of 1.0.0: you don't need to do this any more and we don't ask you to.

I'm on an older version (0.9.5); how do I fix the ownership of my /usr/local tree?

EDIT: I know how to `chown`, I mean more, what can I give back to root, what needs to remain under homebrew's control? Does the new version ship with a tool/command that does this?

Post reply on HN