News for hackers. Stuff that matters.
Re:Curl to shell isn't so bad by dmitriid on Saturday November 09, 2019 @05:49AM (#21490751)
What’s the difference between a curl you blindly pipe into sh and a blind brew install/npm install command?
Re:Curl to shell isn't so bad by sigjuice on Saturday November 09, 2019 @02:01PM (#21493513)
Based on experience, brew will place files in a place that I expect.

I can’t predict where a shell script will scribble or what other changes it will make to my system.

Re:Curl to shell isn't so bad by dmitriid on Saturday November 09, 2019 @06:56PM (#21495385)
A brew recipe is a ruby program that can do anything on your computer. It will and does invoke any number of external processes, including: downloading and executing other recipes, running any number of compilers, arbitrary binary executables, and shell scripts, creating and linking executables, overriding system-provided binaries and libs, etc. etc. etc.

All these recipes and scripts are supposedly downloaded from GitHub. With supposedly anonymous user analytics: https://github.com/Homebrew/brew/blob/master/docs/Analytics....

Re:Curl to shell isn't so bad by jonathanwall on Saturday November 09, 2019 @03:25PM (#21494097)
isn't brew itself a curl'd script?
Re:Curl to shell isn't so bad by kijin on Saturday November 09, 2019 @11:33PM (#21496412)
Installing brew is basically curl|ruby. But that's somewhat forgivable because you need to install a package manager before you can use a package manager.
Re:Curl to shell isn't so bad by eavotan on Saturday November 09, 2019 @06:56AM (#21490991)
The lack of information. Most install docs tell about installation requirements. One-liners don't.