[Pythonmac-SIG] Universal binary build of py2app application won't run on 10.3.9

[Michael Glassford]

Christopher Barker wrote:
> Bob Ippolito wrote:
>>>>> Would it be hard to put a little hack in Py2App to include that
>>>>> particular lib, even though it is in /usr?
>>>>>
>>>>> Or better yet, a way to pass in a list of libs you want included
>>>>> regardless of their location.
> 
>> It's a bad idea, and redistributing components of OS X isn't legal  
>> anyway.
> 
> OK, I understand the legal issues -- darn it!
> 
> However. This is a problem, and there appears to be no solution, other than:
> 
> 1) Don't support 10.3.9
> 
> or
> 
> 2) Wait for Ronald, out of the goodness of his heart, in his free time, 
> to hack the Python build and put out a new version.

Or, as we're considering, have separate Panther and Tiger builds until 
Python 2.5 (which is supposed to have this fix already in it) is 
released. It's scheduled for August, I believe.

I agree, though, that it would be nice if there were a way for "mere 
mortals" to deal with problem libraries on their own.

> 
> I'm guessing that this may not be the ONLY lib that has this problem -- 
> it's just the the one that's been discovered. Also, it seems possible 
> that a user might have a similar problem with a lib that isn't Apple's.
> 
> While I understand that the legal issues are such that we shouldn't 
> include that lib be default, having a hook so that the user could 
> specify libs they wanted included by hand would be helpful. In this 
> case, it wouldn't be a big deal to build your own copy of the bz2 lib 
> and include that.
> 
> Could you just copy such a lib into your bundle after the fact? If so -- 
> where?
> 
> -Chris

Mike