Hi,
>
>> I still maintain my basic argument that it is not ideal for root to just >> assume 'python' found via the PATH is always the right binary to use.
I've checked with the MacPorts Gurus, and the bottom line is the problem (as far as we are concerned) is with the root build assuming 'python' is always the name of the binary python. We need to be able to set this to something else, like pythonN.M.
I understand your point above. I am not though asking for a change to the default behaviour that would affect these novice users. Just a (as hidden as you want) way of telling the root build that the python binary name is something other than 'python'.
Aren't things already inconsistent. Options are provided to define precisely define to ./configure the include and lib dir for python, but not to change the binary name. For me, this these go together and to provide one but not the other is a little inconsistent.
If I cannot convince you to provide someway to make this configureable then fine, we will have to agree to disagree. Shame, as it will mean the root port in MacPorts will not work with python as well as it could.
cheers Chris
This archive was generated by hypermail 2.2.0 : Wed Sep 14 2011 - 23:50:01 CEST