[Pythonmac-SIG] Re: Python Framework vs 'traditional' was Re: version numbers and dependencies

[Michael Maibaum]

On 17 Dec 2004, at 16:08, Markus Weissmann wrote:

> On Dec 17, 2004, at 16:58, Bob Ippolito wrote:
>
>>
>> On Dec 17, 2004, at 10:26 AM, Markus Weissmann wrote:
>>
>>> On Dec 17, 2004, at 16:04, Bob Ippolito wrote:
>>>
>>>> Yes, default on darwin/mac os x is what we both meant :)
>>>
>>> did someone already tried to compile python 2.4 with  
>>> --enable-framework _and_ tried
>>> to destroot the install?
>>> It seems utterly broken - some stuff relies on already installed  
>>> files which are - of course -
>>> not yet in the installdir but inside the destroot...
>>>
>>> ./python.exe ./Mac/scripts/BuildApplet.py \
>>>         --python  
>>> /opt/local/Python.framework/Versions/2.4/Resources/Python.app/ 
>>> Contents/MacOS/Python \
>>>         --output  
>>> /opt/darwinports/dports/lang/python24/work/destroot/Applications/ 
>>> MacPython-2.4/BuildApplet.app \
>>>         ./Mac/scripts/BuildApplet.py
>>> Traceback (most recent call last):
>> ----
>>> IOError: [Errno 2] No such file or directory:  
>>> '/opt/local/Python.framework/Versions/2.4/Resources/Python.app/ 
>>> Contents/MacOS/Python'
>>
>> That's going to be a mess to fix, bundlebuilder is an ugly mess of  
>> code that never really worked quite right in the first place -- which  
>> is why py2app exists.  Current versions of py2app would have a  
>> similar problem, though, because for "lightweight" semi-standalone  
>> application bundles it would expect to find the Python runtime in its  
>> current location, not its future location.  I'll see about adding an  
>> option similar to "--python" that allows you to override its  
>> preference for a Python runtime location before py2app 0.1.7 is  
>> released.
>>
>> For now, I would recommend not running "make frameworkinstallextras".  
>>  The "extras" it installs are mostly garbage anyway (an Applet  
>> building tool that doesn't quite work very well, an ancient IDE  
>> without syntax highlighting, etc.), most of them won't work unless  
>> WASTE was around during compile time (which it probably isn't), and  
>> we're not losing any functionality from the current default build  
>> style.
>>
>
> ok - I did a "make frameworkinstall" - is there a straight way to  
> suppress installing the extras?
>

Ok, here is a version that appears to work, I've basically just patched  
the OSX specific Makefile to only do the install_Python installation  
target, + some moving around of files that ignore prefix.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: Portfile
Type: application/octet-stream
Size: 1489 bytes
Desc: not available
Url : http://mail.python.org/pipermail/pythonmac-sig/attachments/20041221/bb45cf2a/Portfile-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch-osx-Makefile.diff
Type: application/octet-stream
Size: 456 bytes
Desc: not available
Url : http://mail.python.org/pipermail/pythonmac-sig/attachments/20041221/bb45cf2a/patch-osx-Makefile-0001.obj