Hello,
I read that ticket and assumed it was a problem with 1.7rc1 based in
the title of the ticket.
macports 1.7rc1 writes path variable to .tcshrc even when a .cshrc is
present
Another Sys Admin and I modified the existing .tcshrc file to no
avail. There was no .cshrc file, so I may try doing that next.
But again, I thought this was a problem with the new RC version of
Macports, _not_ 1.6 stable, which is what I installed.
Thanks,
Eliot Lee
On Dec 9, 2008, at 12:36 PM, Joshua Root wrote:
List Acct wrote:
Hello All,
Yesterday I installed Macports 1.6 in a Powerbook running Leopard
10.5.5
in one of our user's computers, so that I could install ImageMagick
more easily.
After installing it, her cshrc shell environment was hosed.
When she typed in echo $PATH, the Macports directory was returned.
/opt/local/bin
which had been added in her .bash_profile file, but she is not
using bash.
So, the temporary fix was to create a shell script that sets
environmental variables.
How do I permanently fix this problem without uninstalling Macports?
Uninstalling MacPorts won't help (if you follow the usual
instructions),
this is a shell configuration file issue. It sounds similar to what
was
reported in this ticket: <http://trac.macports.org/ticket/17588>
From a quick glance at the man page, it doesn't appear that tcsh will
read .bash_profile, so that won't be the problem. If it's the same
problem as in the ticket, a new .tcshrc will have been created with
the
MacPorts environment stuff, thus causing .cshrc to be ignored. The
solution would thus be to combine .tcshc and .cshrc into one file.
- Josh
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
