341–350 of 516 posts
I don't understand if there are implications to upgrading to homebrew 3.0 for me a lowly user. Will things break? Will I lose access to formulae that haven't yet been upgraded to work with brew 3.0? Should I upgrade right away or hold off for a while? Which is least likely to interupt my workflow in which I count on brew just working?
Earlier quoted context omitted.
It saddens me as I see this massive infusion of developer time and energy being donated to one of the biggest tech companies around. If that effort had instead gone into making Linux better, which Homebrew obviously builds on, where would Linux workstations be now? Would I get a nice Linux laptop from my company instead of being forced to use a MacBook?
Contributing to Linux also helps the biggest tech companies around - namely IBM and Oracle amongst a host of others. When you contribute to free and open source software you should know and understand you're providing your labor for free to tech behemoths. For most it's a labor of love and aligns with their passion and so everything is cool but you run across a few who's feelings get hurt and feel like they're gettin…
Earlier quoted context omitted.
Yes, he posted more information in an answer on Quora[1] to clarify why he felt he was turned down. [1]: https://www.quora.com/Whats-the-logic-behind-Google-rejectin...
> But ultimately, should Google have hired me? Yes, absolutely yes. I am often a dick, I am often difficult, I often don’t know computer science, but. BUT. I make really good things, maybe they aren't perfect, but people really like them. Surely, surely Google could have used that. Actually, no. There's no level of rockstarness that excuses being a dick and difficult to work with. That kind of attitude can turn a who…
But does it still try to update literally every time you use it?
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.
Macports? They’ve been around even longer than brew. But they were always a bit too Linuxy for most Mac users.
One thing I haven't seen mentioned here is that Homebrew forced people use Ruby to write formulas (ie packages), whereas MacPorts forced people to use Tcl. This one decision, plus hosting formulas on Github, was a major contributor to their present success. As much as I sympathize (deeply) with all the criticism of Homebrew here on this thread -- I used to use MacPorts religiously and love it -- I don't think Homebre…
Those were one of the reasons, but I believe the biggest reason was MacPorts didn't install from binary archive and requires building everything from source in its early days (in the old BSD port tradition). Binary archives were added to MacPorts in 2011 with MacPorts 2.0, but a lot of people (me included) has already moved to Homebrew, leaving MacPorts with an impression of old, slow, and make your Mac fry an egg. M…
The majority of the ports and software I want installed are essentially Unix/Linux/GNU environment tools. Macports has always seemed to me to be a more "unix-y" way of doing that, and it works politely with Apple's ways on top of the Unix core (eg locking down the system volume). It also has a very nice "select" and "variants" system that allows you to have multiple versions of a package as well as packages with more…
Why is it bad that homebrew puts files in /usr/local? Edit: They use /opt if you're on Apple Silicon https://github.com/Homebrew/brew/blob/master/docs/Installati...
I think my mistake was treating it like any other unix-y [multi-user] system, because I installed everything with one account, then created a dedicated 'build' account for the agent to run as -- exactly as our linux (and even, ahem, Windows) agents were setup. This caused all kinds of failures for the 'build' user as everything was owned by and had permissions setup for the first user.
I came away kind of disgusted at the horrible patterns in use. Windows has spent two decades cleaning up that mistake, and here's a comparably new system making the same, awful mistakes?
User-writable/owned stuff goes in ~. Period.
Earlier quoted context omitted.
That is frustrating, but fortunately `HOMEBREW_NO_AUTO_UPDATE=1` will take care of it. Then you have to remember to update every now and then yourself, though.
Would you happen to know how to disable upgrading unrelated packages? I often do `brew upgrade X`. Brew indeed does what is necessary to upgrade package X + deps. But then goes on and starts upgrading unrelated packages.
Packages have dependencies, and those dependencies have dependencies. Try `brew deps ---tree x` to see all the dependencies for you package.
Look at `brew pin` to pin packages you don't want brew to upgrade.
Many formula are versioned. For example if you install `postgresql` it will do major upgrades of postgres as they become available, but if you install `postgres@9.6` it will only install updates to 9.6.
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.
export HOMEBREW_NO_AUTO_UPDATE=1
Earlier quoted context omitted.
> found it a bit cumbersome with the “no sudo” requirement This is one of the few features I do love about Homebrew. Does MacPorts have a "no sudo" mode or does it just let all packages run rampant on your system?
The problem is that the way they do it breaks the UNIX model. /usr/local is common to all users, but Homebrew gives it the current user's permissions. This consequently creates weirdness if you actually use multiple user accounts.