macport's oddity

[Kevin Walzer]

On 9/20/09 1:41 PM, Jack Howarth wrote:
> On Sun, Sep 20, 2009 at 05:12:57AM +0000, Eric Hall wrote:
>>
>> 	Did you bother to check your PATH in those
>> terminal windows where things didn't work?  If you
>> did, did it have /opt/local/bin:/opt/local/sbin
>> in it?  If so, then that's a bit odd, but at a shell
>> and/or system level, not something that MacPorts
>> is doing.  If not, then it sounds perfectly normal
>> for a shell.
>>
>>
>> 		-eric
>>
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
>
> The PATH is showing...
>
> [Macintosh-2:~] howarth% printenv PATH
> /opt/local/bin:/opt/local/sbin:.:/usr/local/NMRPipe/nmrbin.mac:/usr/local/NMRPipe/com:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/bin
>
> It seems obvious that it had to be set otherwise opening a
> new Terminal window wouldn't solve the issue. I'll
> try bash to verify that problem disappears under that
> shell. It is a really odd glitch as I've never seen
> tcsh not 'find' new files after a rehash but require
> a new Terminal window. FYI, this is under Snow Leopard.

Doesn't Fink source an "init.sh" file that modifies your path on the fly?

#test -r /sw/bin/init.sh && . /sw/bin/init.sh

MacPorts doesn't do this, it simply adds /opt/local/bin to the $PATH 
defined in your ~/.profile, which won't show up until a new Terminal 
session is open.

--Kevin

-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com