python24: Remove references to Fink's /sw

[blair (Blair Zajac)]

Currently on my system, I have Fink installed in /sw and am building out a new Darwin Ports build:

In the Python2.4.2 setup.py are references to Fink's /sw:

Ashley-Rothschilds-PowerBook-G4-15:/bztmp/Python-2.4.2 blair$ find . -type f -print0 | xargs -0 grep /sw/ ./Mac/OSX/PythonLauncher/factorySettings.plist: <string>/sw/bin/pythonw</string> ./Mac/OSX/PythonLauncher/factorySettings.plist: <string>/sw/bin/pythonw</string> ./Mac/OSX/PythonLauncher/factorySettings.plist: <string>/sw/bin/python</string> ./Mac/OSX/PythonLauncher/factorySettings.plist: <string>/sw/bin/pythonw</string> ./Mac/OSX/PythonLauncher/factorySettings.plist: <string>/sw/bin/python</string> ./Misc/NEWS:- On Darwin/Mac OS X platforms, /sw/lib and /sw/include are added to the ./setup.py: add_dir_to_list(self.compiler.library_dirs, '/sw/lib') ./setup.py: add_dir_to_list(self.compiler.include_dirs, '/sw/include') ./setup.py: '/sw/include/db4', ./setup.py: '/sw/include/db3',

It would be good to remove the /sw references, otherwise Darwin Ports' Python may go looking in there for modules, which I'd rather not see.

In many of these same locations, there are no references to Darwin Port's /opt/local locations, so maybe the patch can s#/sw/#${prefix}#/.

Regards, Blair

[markd@…]

The Python programmers have their own agenda and if we patched and removed this we'd have to repeat this for every version of Python as they were released. So I think we'll have to let the Python folks work this out over time as they see fit. Thanks for being willing to contribute.

[blair (Blair Zajac)]

Well, you're mixing several different issues here.

One is the patching thing. We patch all the time in DP, so I don't see the value of this point. And the patches will probably apply cleanly to newer versions of Python. And even if they don't, a recursive grep would find all /sw occurances.

I also don't see what point about the Python developers. We patch things to suite DP all the time also, irrespecitive of the developers choices.

And finaly, I find it odd that you would want a DP Python build to inadvertenly use resources from Fink. It's one thing to depend upon OS X libraries, but to depend upon another package mangement system which may be removed, changed or modified outside the scope of DP doesn't seem like a wise decision. What's the point of a packagement system when the dependencies can be removed without port's knowledge.

Regards, Blair

Regards, Blair