[deleted]
Homebrew 1.0.0
171–180 of 255 posts
Re: Homebrew 1.0.0
#172Earlier quoted context omitted.
I just do this for now: cat brew_install.txt It lists directly from brew, prepends brew install and then replaces all newlines with a space and outputs to brew_install.txt
I use brew leaves instead of brew list for this sort of thing; as I usually don't care about the constituent transitive dependencies, only the final results.
I wasn't even aware of existence of that!
Re: Homebrew 1.0.0
#173Among all the software I use, Homebrew must be the one giving me the least trouble. I have 100 installed packages and I don't remember the last time anything didn't work. Plus, for anything I care about, updates seem to always take less than a day, usually it's almost instantaneous. In comparison with MacPorts before, it's like night and day. npm/pip/mix/bundler all seem to periodically conspire to waste a few hours…
pip is atrocious/dangerous on any system without virtualenv. I've managed to sort this by using virtualenvs where I can and homebrew Python + packages when I can't (numpy, etc.). Two things really help: pipsi ( https://github.com/mitsuhiko/pipsi ), which installs tools inside their own virtualenv and PIP_REQUIRE_VIRTUALENV, which stops pip from working outside a virtualenv.
You could try conda. It's basically a pip and virtualenv that works on non-Python dependencies.
Re: Homebrew 1.0.0
#174Earlier quoted context omitted.
It's hard for me to understand the issue with this. Google didn't hire the guy who wrote software that had a big impact on the community. Does it mean Google misses good engineers because of their less-than-ideal interview process, or simply Google hires only people who are a good fit for their organisation? Writing the overly bitter tweet surely won't help with improving hiring points. Seems highly unprofessional an…
I'm sorry, but I am sick and tired of "unprofessional" just thrown around like this. The person is a god damned human being, not a robot. They had just gone through an extremely frustrating experience with an unsatisfying conclusion. And it's Twitter. The only one who's being unprofessional is the one chiding others for being "unprofessional".
I've never publicly called out a company that rejected me. It's not that hard to exercise some self-restraint.
Re: Homebrew 1.0.0
#175Earlier quoted context omitted.
As someone who maintain a ROS installation scheme for Mac based on homebrew ( https://github.com/mikepurvis/ros-install-osx ), this is a constant source of frustration. Even a fairly vanilla ROS installation has a deep dependency tree— there are any of several dozen major packages which can at any moment release a new major version and break us.
If you rely heavily on Homebrew in this way you should instead vendor all the formulae you depend on so that updates do not happen without your manual intervention.
Exactly. That's how I managed an app (basically a port of lots of stuff from Linux) for macOS years ago. I depended upon MacPorts as my build system, lots of patching to match our in-house build on Linux... but wrapped an entire Python etc universe inside the app.
Re: Homebrew 1.0.0
#176Earlier quoted context omitted.
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.
Sorry, I probably failed to notice the "Thanks Homebrew team. <3" part first time round.
[deleted]
Re: Homebrew 1.0.0
#177Brew 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 obviously fine for you to do but it's worth noting that we remove software that no-one uses where "no-one" is defined by "no-one using analytics". That's actually our main use-case for analytics.
Opt-out tracking is unjustifiable no matter how convenient it may be for the developer.
Re: Homebrew 1.0.0
#178Earlier quoted context omitted.
That's obviously fine for you to do but it's worth noting that we remove software that no-one uses where "no-one" is defined by "no-one using analytics". That's actually our main use-case for analytics.
> we remove software Why? Personally, the only reason I would remove software from a repository is if it didn't work, impacted performance, or cost me an unreasonable amount of money/time. There's a really long tail for software packages.
In short: we generally only remove things when they break, break other things or the projects are dead. How hard we try to fix these things generally come down to how used our analytics say they are.
Re: Homebrew 1.0.0
#179I've had few (minor) issues with Homebrew, so I've been wondering about pkgsrc. Has anyone tried using pkgsrc, as a replacement for Homebrew?