Opened 13 years ago
Closed 13 years ago
#33379 closed defect (invalid)
MacPorts 2.0.4 modifies default bash profile behavior
Reported by: | a.y.harano@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | |
Keywords: | Cc: | ||
Port: |
Description
It seems that MacPorts 2.0.4 installs a .profile to ease the setting of PATH, pointing to port's installed binaries first, which is great.
However, it altered the default behavior, somehow involving PS1. I would like to know how to correct it.
In my case, it first appeared
M~ y$
and now it appears
151~ y$
Change History (5)
comment:1 Changed 13 years ago by a.y.harano@…
Cc: | a.y.harano@… added |
---|
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | a.y.harano@… removed |
---|
Replying to a.y.harano@…:
It seems that MacPorts 2.0.4 installs a .profile to ease the setting of PATH, pointing to port's installed binaries first, which is great.
All versions of MacPorts have done that; it's not new for 2.0.4.
However, it altered the default behavior, somehow involving PS1. I would like to know how to correct it.
That doesn't sound intentional... MacPorts should have backed up your .profile; you can compare the before and after to see the changes and see if anything looks wrong.
comment:3 Changed 13 years ago by a.y.harano@…
I didn't find any kind of .profile backed up. I guess I didn't have one before upgrading to 2.0.4 or installing MacPorts. I don't have my Time Machine here to compare if it previously had.
Except for .profile, what else could cause this? If it matters: I killed port while it was upgrading but followed by redoing it.
comment:4 Changed 13 years ago by a.y.harano@…
It seems to be solved here somehow after rebooting two times after upgrading MacPorts.
You may close or delete this ticket. Sorry for disturbing the support staff.
comment:5 Changed 13 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Cc Me!