sudo /opt/local/bin/port selfupdate worked like a charm so now I know I'm alive and gotta fix the .profile. I will dig further as per your subsequent message and bore all with the details of what will probably will be my possitive findings from this point forward at least with regard to mac ports. Zope is another matter ugh.
----- Original Message ----- From: "David Poehlman" <[EMAIL PROTECTED]> To: "General discussions on all topics relating to the use of Mac OS Xby theblind" <[email protected]> Sent: Thursday, January 10, 2008 8:26 AM Subject: Re: plone same problem as mac ports: The path doesn't help. I put the path in my .profile and checked to see that it was still there after opening a new shell and it is but still no go. even if I am in the directory where the thing resides, I cannot get it to work. I agree it's a path issue, but thin that for some reason, my Macs are blocking my attempts to provide input to the path process. Thanks for the direction on this though, I'll look into it further. ----- Original Message ----- From: "Cheryl Homiak" <[EMAIL PROTECTED]> To: "General discussions on all topics relating to the use of Mac OS Xby theblind" <[email protected]> Sent: Thursday, January 10, 2008 8:08 AM Subject: Re: plone same problem as mac ports: Ok, that means it isn't in your path. What are you specifically typing in macports and wht happened when you typed sudo /opt/local/bin/port selfupdate or sudo /opt/local/bin/port upgrade installed I was under the impression we had solved this prolem for you with the tip about the path; if not, post what's going on and i'll be happy to try to help you. I'm sure it's probably the same problem with this other program you've installed.
