>> On Tue, 2008-03-25 at 19:48 -0700, James Peach wrote:
>>> - /usr/contrib/bin /opt/local/bin
>>> + /usr/contrib/bin
>>
>> You really don't like this bit do you? :) ... I think
>> since we have /usr/local/bin for Linux, we should also
>> do this for consistent behaviour on Mac.
>
>
> Yes, I *really* hate it :)
>
> First, OS X has 2 possible sources of additional software - MacPorts
> and Fink. MacPorts installs in /opt/local and Fink (IIRC) installs in /
> fw.
OK, thats not an argument for removing it though.
> Second, as a matter of policy I don't think that PCP should be using
> random tools from all over the system.
Its not random, its very specific, and its meant to cover the places that
configure is going to go look for binaries (I think).
Personally, I don't like this & tend to agree with you, but the reality is
thats how all of the ports have been done. And I don't think there's
much reason to deviate from that for one particular port - the only
real options are to either fix it for all (i.e. remove all the "special" case
PATH additions) - a QA nightmare - or tow the line.
> Third I think that the whole concept of searching the $PATH of the
> person who ran configure is wrong. If PC is going to search the
That's not what pcp.env is doing (though its not clear what you meant by
"PC" above).
> builder's $PATH, then it should update the PATH in pcp.env. Otherwise
> it should only search the path in pcp.env, since that is what will be
> searched at the time when these tools are actually needed.
cheers.
--
Nathan
|