#20524: base-1.7.1 Neater PATH change process for Postflight ---------------------------------+------------------------------------------ Reporter: alex@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.1 Resolution: wontfix | Keywords: PATH profile postflight Port: | ---------------------------------+------------------------------------------ Comment(by alex@…): Fair enough, it was just an idea. I've just checked my system out and even though I've ensured that the MacPorts paths are at the beginning of the /etc/paths file, they're still not first in the $PATH variable even though the path_helper script ought to process them in order, so you're right, it'd need more tweaking and perhaps be just as much work as the current method. Interestingly, though my /etc/paths file contains the two MacPorts paths *first*, then the defaults, then /usr/local/bin (it looks like this): /opt/local/bin /opt/local/sbin /usr/bin /bin /usr/sbin /sbin /usr/local/bin - the process output from /usr/libexec/path_helper -c is: setenv PATH "/usr/bin:/bin:/usr/sbin:/sbin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/X11/bin"; setenv MANPATH "/opt/local/share/man:/usr/share/man:/usr/local/share/man:/usr/X11/man"; which is weird since I've put the MacPorts paths first, but it's skipped those, put the default paths in first, then the MacPorts paths, and then the /usr/local/bin at the end - before it started processing anything in the /etc/paths.d folder. I'll see if I can work out how this is working, as it's not immediately clear from the path_helper script. Thanks for the quick response and consideration though. Best regards, Alex -- Ticket URL: <http://trac.macports.org/ticket/20524#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS