On Apr 2, 2013, at 7:22 PM, Ryan Schmidt wrote:
>
> On Apr 2, 2013, at 21:00, Ryan Schmidt wrote:
>
>> 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.
>
> The code the installer runs to
On Apr 2, 2013, at 21:00, Ryan Schmidt wrote:
> 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.
The code the installer runs to set up your .profile is here, by the way:
https://trac.macp
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 ~/.pro
Hey Folks,
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:
---