In my experience, most software for OS X that installs cli components installs to /usr/local/
and then creates symbolic links to executables in /usr/local/bin/
, as not to modify my $PATH
. However, the Go installer differs in approach by creating a new entry in /etc/paths.d/
for path_helper
to read and then modify my $PATH
. Can someone please explain the thinking behind this design decision? Is it more common on Linux to have a lot of path additions instead of symbolic links to executables in an existing directory?
I'd love to get a better understanding of why this choice. I have never seen another software take this approach.