Re:Detecting the use of “curl – bash” server side
by merb on Wednesday April 20, 2016 @06:20AM
(#11533346)
Actually 99% of the Time this will install it to /usr/local
[ Parent
| on HN ]
Re:Detecting the use of “curl – bash” server side
by fjarlq on Wednesday April 20, 2016 @06:32AM
(#11533387)
I disagree. Many (probably most) makefiles conform to the GNU Coding Standards, which recommend declaring "all" to be the default make target. `make all` does not install; that's what `make install` is for.
https://www.gnu.org/prep/standards/html_node/Standard-Target...
Re:Detecting the use of “curl – bash” server side
by coldtea on Wednesday April 20, 2016 @06:46AM
(#11533446)
The idea of the original parent comment on Make is not about well conforming makefiles.
The idea is that if one doesn't trust a random curl-ed install file, they shouldn't trust a downloaded makefile either -- and for the same reasons, yet tons of people complaint about the first, but have been using the latter for decades without complain...
Re:Detecting the use of “curl – bash” server side
by coldtea on Wednesday April 20, 2016 @06:43AM
(#11533432)
The idea is that the Makefile (and maybe configure?) could just as well as a "curled" install script contain ANY command, even "sudo rm -rf /".
It's not about where it will install it if it works fine.