Added support in MacPorts base to set PATH and MANPATH automatically in Leopard

[James Berry]

Hey Kevin,

On Nov 29, 2007, at 1:49 PM, Kevin Van Vechten wrote:

> I as understand it, appending /opt/local/bin to the path works fine  
> at _runtime_ but may be insufficient at _build time_.

So you're saying that if we append prefix to the path we might have  
build issues that we wouldn't have if we prepend. That's a good  
argument.


> It seems to me that MacPorts should explicitly set the path to  
> what's needed at build time (i.e. prepend $prefix to PATH) ... as  
> the PATH might not even include /opt/local at all.
>
> - Kevin
>
> On Nov 29, 2007, at 1:27 PM, Kirk Kelsey wrote:
>
>>
>> On Nov 29, 2007, at 2:43 PM, James Berry wrote:
>>> I think it's a question for the group in general: which is the  
>>> best approach? The range of choices we have is basically to pick  
>>> from the following menu:
>>>
>>> 	- Install a file into /etc/manpaths.d/
>>> 	- Install a file into /etc/paths.d/
>>> 	- Munge ~/.profile to munge MANPATH
>>> 	- Munge ~/.profile to munge PATH
>>
>>
>> was
>> 	- Munge /etc/[man]paths
>>
>> ruled out? It has the advantage of letting us put /opt/local/ 
>> {bin,man} in the [MAN]PATH where we want it and being much easier  
>> to work with than shell rc/profile files.
>>
>>
>> Kirk
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo/macports-dev
>