On Apr 2, 2013, at 20:44, Christopher Stone wrote: > I was having a discussion about paths with someone and looked at mine because > of it. > > What I found was a bit surprising; there are several duplications — and it > appears to my inexpert eye that MacPorts is the culprit. > > From ~/.profile: > > ------------------------------------------------------------------------------------------- > > /opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin > > ## > # Your previous /Users/chris/.profile file was backed up as > /Users/chris/.profile.macports-saved_2012-05-15_at_14:27:56 > ## > > # MacPorts Installer addition on 2012-05-15_at_14:27:56: adding an > appropriate PATH variable for use with MacPorts. > export PATH=/opt/local/bin:/opt/local/sbin:$PATH > # Finished adapting your PATH environment variable for use with MacPorts. > > > ## > # Your previous /Users/chris/.profile file was backed up as > /Users/chris/.profile.macports-saved_2012-08-06_at_09:41:10 > ## > > # MacPorts Installer addition on 2012-08-06_at_09:41:10: adding an > appropriate PATH variable for use with MacPorts. > export PATH=/opt/local/bin:/opt/local/sbin:$PATH > # Finished adapting your PATH environment variable for use with MacPorts. > > ------------------------------------------------------------------------------------------- > > I'm assuming I can safely delete one of these entries.
Yes. > Could this have been done by the 2.0 beta and then the 2.0 release versions? The code that changes your .profile hasn't really changed in a long time. It should not have added to your .profile if the path was already set properly. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users