Earlier quoted context omitted.
1) You could also create some wrapper scripts setting the path, or have someting inspired by virtualenv handle it, or maybe different terminal profiles. Those breakings really are edge cases. 2) Don't put them in the PATH. They're prefixed with 'g' so you can make an non-prefixed alias for your interactive shell, and use the prefixed variant in your scripts if need be. If you write portable scripts you're either usin…
1) Well, I could do I suppose. That all sounds a bit complicated however. 2) I am not talking about my own scripts, I am talking about other peoples. I could obviously go through and debug them, and then check I haven't broken them on a couple of linuxes, and a mac without macports/homebrew but... I don't want to. 3) You are right, it looks like gcc and gdb have both been taken out of homebrew, I assume because they…
Which is why the alias solution is nice, as it will only impact the interactive shell, not the scripts.