5 comments

[ 2.3 ms ] story [ 19.8 ms ] thread
Can someone ELI5 what we're supposed to see here?
I may be wrong, but I think the point of this post is to show that all of these projects are losing a degree of portability by making the assumption that the `git` binary lives in `/usr/bin` on its target platform. There are many *nixes (like most BSDs, afaik) for which this assumption is incorrect.

EDIT: If that’s actually the goal here, though, I think this example doesn’t really make a solid argument. A ton of these results are from people’s personal dotfiles or from projects that have separate files for platforms that don’t keep `git` in `/usr/bin`.

Ah... I see. I suppose that kind of makes sense.

However, as you mentioned, I see plenty of people's personal config files, such as the many sublime text settings folders, or other .xml files.

I think it may have something to do with this? http://rachelbythebay.com/w/2016/04/17/unprotected/

Apple git has a security vulnerability. In the new OSX the user cannot modify /usr/bin by default so even if they have installed a secure version of git the insecure one is executable at /usr/bin

Why not use `env git` at all?