3 ms·
My experience is that software that installs via curl|bash tends to ignore my preferences as expressed via $PREFIX/DESTDIR, $XDG_{CACHE,CONFIG,DATA}_HOME, etc.
by andreareina 7y ago
My experience is that software that installs via curl|bash tends to ignore my preferences as expressed via $PREFIX/DESTDIR, $XDG_{CACHE,CONFIG,DATA}_HOME, etc. It'll install who-knows-where and probably leave dotfiles all over my home directory.
Maybe curl|bash is functionally equivalent to git clone && ./configure && make && make install, but my bet is on the one providing a standard install flow to be a better guest on my system.
- manojlds 7y agoThe curl|bash might actually clone a repo and build it. Your concern is a different one.
- marcosdumay 7y agoYes, it could. But it that was the case, the site would say one can just clone the repo and build it instead of sending everybody into the curl route.
- ilaksh 7y agoSome of them do say that.
- theamk 7y agoyep, and that would be bad! If clone / build steps are separate, I can at least verify the hash looks sane, or mirror it locally, etc.. In the curl|bash approach, all of this is lost.