On Tue, Feb 2, 2016 at 10:22 AM, Harald Hanche-Olsen <han...@math.ntnu.no> wrote:
> Okay, now I am curious. How does the macports installation manipulate the > path? As far as I know, the above method is standard, even though it may > not be what macports does. (If I installed that file there, I must have > done it because it didn’t work otherwise.) 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. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
