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

[James Berry]

Hi Juan,

On Dec 2, 2007, at 9:50 AM, Juan Manuel Palacios wrote:
> 	So, has any conclusion been reached for this issue? I'm inclined to  
> backing this feature out of the release_1_6 branch until a working  
> consensus is reached, and only release it to the public at that time  
> (in 1.6.x (x > 0)). Until now we've only been modifying the user  
> "profile" for a range of bourne based shells and the "cshrc" file  
> for equivalent C based shells, which has worked fairly well, I  
> believe; anyone experienced enough to create something like  
> ~/.bash_profile or anything else very shell specific would be savvy  
> enough to setup his/her own environment to their content, I'm sure.  
> I'd strongly favor sticking to this approach in 1.6.0 until  
> something better is found, unless it explicitly breaks expected  
> behavior on Leopard. Does it?

Well, given that man pages are broken at present with a standard  
MacPorts install under Leopard, something has to be done. A few choices:

	(1) Use this scheme, as implemented. (Downsides: affects /etc,  
MacPorts paths are added at the end of PATH and MANPATH).

	(2) Supplement this scheme by munging PATH inside the MacPorts code  
to ensure that $prefix is always at the head of the path during  
builds, and to guard against the sort of build problems suggested by  
kvv.

	(3) Modify existing path modification code to also add MacPorts paths  
to MANPATH. (This might break other man pages on Tiger where the  
system provides no meaningful default for MANPATH—maybe we do it only  
if MANPATH is already defined?)

I've been mulling over this situation for the last week or so, but  
haven't done anything because I'm not very happy with any of the  
solutions.... I think (3), however is the lowest risk approach.

James