-----Original Message----- From: Brandon Allbery <[email protected]> Date: 2 February 2016 at 16:28:50
> The problem with paths.d is that it adds path entries *after* the standard > ones, whereas users tend to expect that e.g. /opt/local/bin/python > "overrides" Apple's /usr/bin/python. So MacPorts edits your .bash_profile > or .profile to prepend /opt/local/bin to $PATH. Ah. That explains it; thanks. And that doesn’t work for me because I don’t use bash for my login shell, which would be why I made my own hack. An alternative would have been to modify /etc/paths instead? Or is that too global, or something? – Harald _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
