On Apr 8, 2009, at 12:03 PM, Rainer Müller wrote:
The problem is that frameworks allow to contain multiple versions, but the compiler does not have any option to choose a specific version. Inmy opinion this is a bug. But given this fact, all ports wanting to linkagainst python need to be patched not to use -framework. This has already been done for example for mod_wsgi and mod_python25 by commenting out the framework relevant parts in the configure script.
Ok, I can do that for the subversion-python25bindings port too, then, I guess.
We need to get ports not to use these flags. Either we trick ports not to link using -framework by patching each of them or by modifying the global python configuration not to report itself as a framework. Butthen what would be a reason to keep it as a framework as it causes us somuch troubles? As far as I know the only advantage of the frameworks is currently to have working pythonw and IDLE. Is there really no way to get this without a framework build or did just nobody try yet?
I would also prefer the non-framework install. (I don't know how difficult it would be to get pythonw and IDLE to work, though).
-- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
