[MacPorts] #21625: .bash_profile $PATH handled incorrectly
MacPorts
noreply at macports.org
Mon Sep 28 00:21:40 PDT 2009
#21625: .bash_profile $PATH handled incorrectly
----------------------------------------+-----------------------------------
Reporter: curtis_ovid_poe@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: base | Version: 1.8.0
Resolution: worksforme | Keywords:
Port: |
----------------------------------------+-----------------------------------
Changes (by blb@…):
* status: new => closed
* resolution: => worksforme
Comment:
Replying to [comment:4 curtis_ovid_poe@…]:
> This was set in my .bash_profile. I had to set in manually because when
I first started using Mac Ports (a couple of years ago), I was still not
getting those ports first in my path. I later installed Snow Leopard, I
had a number of corruption issues and had to reistall Mac Ports.
Regrettably, I was fixing so many issues that I can't tell you the steps
to recreate this.
There was a bug in older versions of the MacPorts package that would fail
to update the PATH properly, perhaps that was the source of that issue?
Also, note that reinstalling MacPorts when upgrading to 10.6 (or any major
OS version update) is actually the [wiki:Migration proper method to use].
>
> The implication is that somehow the $PATH got wiped out during my
upgrade and the /opt/local/bin wasn't in my path when Mac Ports was
reinstalled. I don't know how this could have happened, but it sounds
like you are doing the right thing (so long as my $PATH is correct).
If /opt/local/bin wasn't found in PATH at the time of a new install, that
would definitely explain why it decided to update your PATH. If you do
find that that isn't working correctly, say so and I'll reopen the ticket.
--
Ticket URL: <http://trac.macports.org/ticket/21625#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list