Earlier quoted context omitted.
He left.
Source?
Homebrew 1.0.0
91–100 of 255 posts
Re: Homebrew 1.0.0
#92I can see a point in the future where everything is installed via a homebrew-like process. Forget CPAN, CRAN, ports, pypi, go-get, rpm, apt, cabal, crate, opam, ... Just get it from github or similar with homebrew.
Doubtful, homebrew doesn't do any kind of dependency management, so it would be a strict downgrade from pip, gem, cabal, etc Edit: See comment from rogual elsewhere in this thread - https://news.ycombinator.com/item?id=12547076
That's an exaggeration. We definitely do dependency management, we just don't allow formulae in core to pin against arbitrary versions of software because it often means security updates are never tracked. We are going to loosen this slightly but not dramatically: https://github.com/Homebrew/brew/issues/620
Re: Homebrew 1.0.0
#93Be aware of "update bug" If Homebrew was updated on Aug 10-11th 2016 and brew update always says "Already up-to-date". you need to run: ``` cd "$(brew --repo)" && git fetch && git reset --hard origin/master && brew update ``` I had to.
Yep, me as well. Thanks!
Re: Homebrew 1.0.0
#94Brew is awesome. Note though that it gathers anonymous aggregate user behaviour analytics and reports to Google Analytics, see https://git.io/brew-analytics .
You can opt out with
brew analytics offRe: Homebrew 1.0.0
#95Earlier quoted context omitted.
I switched to MacPorts following the Google Analytics debacle [1] and how it was handled [2]. I had this expectation that MacPorts would be backwards and full of ancient packages but it's not - it's fantastic! The package repository is really good, the project itself is stable and it doesn't have a default-on analytics component aggregating my package data at Google. [1] https://news.ycombinator.com/item?id=11566720…
Wow. Thanks for bringing this to my attention. I recently got a new mac and I decided to give brew a spin as my package manager. I was unimpressed with many aspects of the experience- for example, getting weird snarky messages and incorrect advice when I attempted to install texlive- but this seals it. Back to Macports it is. I'll be sure to tell others about this.
I have never had a problem with homebrew. I think some people like one or the other better as a preference though.
Re: Homebrew 1.0.0
#96"brew update Error: /usr/local is not writable. You should change the ownership and permissions of /usr/local back to your user account: sudo chown -R $(whoami) /usr/local . . . ==> Migrating HOMEBREW_REPOSITORY (please wait)... ==> Migrated HOMEBREW_REPOSITORY to /usr/local/Homebrew! Homebrew no longer needs to have ownership of /usr/local. If you wish you can return /usr/local to its default ownership with: sudo ch…
I see no problem in this. We need writing permissions to /usr/local to finish our migration (as we always did). Once you finish the migration we (hopefully) never write directly to /usr/local again.
It was a compliment, as mentioned in other comments. I love the fact that it just doesn't error out, it offers a fix right there. It also humbly offers to surrender the rights to directories it no longer need. Coming from recent Dropbox helper agent debacle, I truly appreciate the philosophy behind this and applaud the team.
Re: Homebrew 1.0.0
#97Just wanted to highlight that as of this release, all the core code for Homebrew-Cask (the sister project for GUI apps) has been (re)integrated into the Brew codebase. This should allow for tighter integration between the two and a renewed focus on making installing GUI apps as painless as possible! From a user/developer perspective, we've created a command line utility (`cask-repair`) to make version bumps as painle…
Looking forward to checking this out. One issue I have run into with homebrew is that due to varying packaging choices as a project grows, I've seen stuff move back and forth from brew core to cask to neither, and the old ones stick around at the outdated version so you have to be careful when you tell people to install the thing (seen this happen with terraform for example, which a month ago when I last checked exis…
We do have a `deprecated` caveat, but we rely on users to bring up that fact, as there's no way the maintainers can keep track of the status of every Cask.
There's also a fairly large push and discussion about removing duplication between Homebrew core and Homebrew Cask, so you should see things improve. There should also be Formula -> renamed Cask migration at some point, the issue has been raised in brew-evolution. (We have basic Cask Formula support already).
Re: terraform specifically, looks like it's now in core, and `brew cask terraform` will know to do `brew install terraform` automatically.
Re: Homebrew 1.0.0
#98"brew update Error: /usr/local is not writable. You should change the ownership and permissions of /usr/local back to your user account: sudo chown -R $(whoami) /usr/local . . . ==> Migrating HOMEBREW_REPOSITORY (please wait)... ==> Migrated HOMEBREW_REPOSITORY to /usr/local/Homebrew! Homebrew no longer needs to have ownership of /usr/local. If you wish you can return /usr/local to its default ownership with: sudo ch…
I see no problem in this. We need writing permissions to /usr/local to finish our migration (as we always did). Once you finish the migration we (hopefully) never write directly to /usr/local again.
so smooth. much wow
Re: Homebrew 1.0.0
#99Brew is awesome. Note though that it gathers anonymous aggregate user behaviour analytics and reports to Google Analytics, see https://git.io/brew-analytics . You can opt out with brew analytics off
That's a thing they shouldn't enable by default, but I don't mind it. As a developer, anonymous usage data has helped me out enough times.
People! Be nice to your fellow developers! When something asks you to send anonymized usage data, do it!
Re: Homebrew 1.0.0
#100Thanks to Mike and everyone else that has contributed to Homebrew. I couldn't imagine how difficult it would be managing command line programs on a Mac without it.
I'm wondering if Macs would be as successful with developers without homebrew.
If it wasn't for Homebrew, I would not develop on a Mac.