81–90 of 216 posts
Homebrew maintainers are doing a fantastic job, made my life as a developer so much easier! I wanna use this opportunity to "publicly" thank them!
Ditto. I install almost everything via brew and brew cask, and store the list of packages in git. It makes setting up a new machine a breeze. Thanks for all your hard work!
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…
Isn't it desirable to run builds as not-root? If you're concerned about safety, you could maybe "freeze" your homebrew install by chowning /usr/local back to root in between brew invocations.
Absolutely. That's why the canonical gnu installation separates "make" from "make install". But homebrew could do the same thing (and maybe it does now -- I need to go back and revisit this because apparently this issue has been resolved.)
Earlier quoted context omitted.
Ditto. I install almost everything via brew and brew cask, and store the list of packages in git. It makes setting up a new machine a breeze. Thanks for all your hard work!
This is a cool idea! How does one go about doing this though? Is there a flag to output a text file with the names of installed versioned packages?
Makes it a lot simpler to do a clean OS install every upgrade, and to make sure all three of my Macs are perfectly in sync!
Homebrew maintainers are doing a fantastic job, made my life as a developer so much easier! I wanna use this opportunity to "publicly" thank them!
Thanks Homebrew maintainers, you make macOS rock even more!
Earlier quoted context omitted.
> Disable running Homebrew as the root user (e.g. sudo brew) why? Just curious, because I always use macports with sudo.
We don't drop privileges when building (as we're not designed to run as root) and the macOS sandbox has issues with the root user so unfortunately you're giving every package you install root access to write to (almost) anywhere on your system. This is bad so we've stopped it.
So why did you choose to disable running as root altogether rather than dropping privileges when building?
Earlier quoted context omitted.
We don't drop privileges when building (as we're not designed to run as root) and the macOS sandbox has issues with the root user so unfortunately you're giving every package you install root access to write to (almost) anywhere on your system. This is bad so we've stopped it.
> We don't drop privileges when building So why did you choose to disable running as root altogether rather than dropping privileges when building?
Earlier quoted context omitted.
> best-practices Wat? How is fundamentally broken dependency management and forcing installed global binaries to be user-owned "best practices"?
Can you rephrase your objection in a less patronising and more constructive way?
Will I need a dongle to use it on my latest macbook? And if so, has the price of it also been cut to a reasonable 19.95?
Yeah, OK. We get it. You don't like something quasi-related to this post. So you're going to get a jab in wherever you can. Good job on you. Enjoy the rest of your week.
Earlier quoted context omitted.
Ah, that is very good to know! Thank you! I will take a fresh look at homebrew. :-)
To perhaps save you some effort: we still ask you to chown e.g. `/usr/local/bin` which may or may not make it unacceptable to you.