> The more I work on supporting 10.3.9 and 10.4 the more I believe
> that the binary installer shouldn't link to system versions of
> libraries that aren't in a part of the OS where Apple is serious
> about versioning/backward-compatiblity.
>
> That is the easiest way to achieve compatibilit
On Jun 30, 2006, at 11:33 PM, William Kyngesburye wrote:
On Jun 30, 2006, at 3:50 PM, Christopher Barker wrote:
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 proble
On Sat, 1 Jul 2006, Ronald Oussoren wrote:
>
> It is rather obvious that nobdy here really cares about 10.3.9. The 2.4.3
> universal installer has been out for ages and there have been test releases
> before the production release and nobody seems to have tested on 10.3.9 until
> now.
>
>
> I
On Jun 30, 2006, at 10:50 PM, 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 i
On Jun 29, 2006, at 9:04 PM, Michael Glassford wrote:
Ronald Oussoren wrote:
On 28-jun-2006, at 20:56, Bob Ippolito wrote:
It's not really trivial, but it's the only option you have unless
someone else does it first. It sounds like Ronald will probably
create another 2.4.3 installer in the
On Jun 29, 2006, at 9:04 PM, Christopher Barker wrote:
Michael Glassford wrote:
"""
Note that dylibs and frameworks
in vendor locations (/System and /usr - except for /usr/local)
are NOT
included in your application bundle.
"""
Would it be hard to put a little hack in Py2App to include
On Jun 30, 2006, at 2:33 PM, William Kyngesburye wrote:
> On Jun 30, 2006, at 3:50 PM, Christopher Barker wrote:
>
>> 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 sim
On Jun 30, 2006, at 3:50 PM, Christopher Barker wrote:
> 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.
>
Here's a lis
On Jun 30, 2006, at 1:50 PM, 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 thei
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 id
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
On Jun 30, 2006, at 12:26 PM, Michael Glassford wrote:
> Bob Ippolito wrote:
>> On Jun 29, 2006, at 12:04 PM, Christopher Barker wrote:
>>
>>> Michael Glassford wrote:
> """
>> Note that dylibs and frameworks
>> in vendor locations (/System and /usr - except for /usr/local)
>> are
Bob Ippolito wrote:
> On Jun 29, 2006, at 12:04 PM, Christopher Barker wrote:
>
>> Michael Glassford wrote:
"""
> Note that dylibs and frameworks
> in vendor locations (/System and /usr - except for /usr/local)
> are NOT
> included in your application bundle.
"""
>> Wou
On Jun 29, 2006, at 12:04 PM, Christopher Barker wrote:
> Michael Glassford wrote:
>>> """
Note that dylibs and frameworks
in vendor locations (/System and /usr - except for /usr/local)
are NOT
included in your application bundle.
>>> """
>
> Would it be hard to put a little
Ronald Oussoren wrote:
> On 28-jun-2006, at 20:56, Bob Ippolito wrote:
>
>>
>> It's not really trivial, but it's the only option you have unless
>> someone else does it first. It sounds like Ronald will probably
>> create another 2.4.3 installer in the future that fixes this and a
>> few other iss
Michael Glassford wrote:
>> """
>>> Note that dylibs and frameworks
>>> in vendor locations (/System and /usr - except for /usr/local) are NOT
>>> included in your application bundle.
>> """
Would it be hard to put a little hack in Py2App to include that
particular lib, even though it is in /usr?
Bob Ippolito wrote:
> On Jun 29, 2006, at 8:20 AM, Michael Glassford wrote:
>
>> Bob Ippolito wrote:
>>> The bz2 module is part of the Python distribution. The best route
>>> would be to download the Python source, extract the source for the
>>> bz2 extension and create a standalone setup.py for i
On Jun 29, 2006, at 8:20 AM, Michael Glassford wrote:
> Bob Ippolito wrote:
>> The bz2 module is part of the Python distribution. The best route
>> would be to download the Python source, extract the source for the
>> bz2 extension and create a standalone setup.py for it. Tweak it such
>> that it
Bob Ippolito wrote:
> The bz2 module is part of the Python distribution. The best route
> would be to download the Python source, extract the source for the
> bz2 extension and create a standalone setup.py for it. Tweak it such
> that it links to a copy of libbz2 that you've compiled statical
Ronald Oussoren wrote:
> On 28-jun-2006, at 20:50, Michael Glassford wrote:
>
>> Ronald Oussoren wrote:
>>> Its getting more and more clear that I can't get way with not
>>> updating the 2.4 installer :-(.
>> Would you be thinking of doing this soon? :)
>
> Not this week, I've spent way too much
Bob Ippolito wrote:
> In your situation, I would just give up on 10.3 users until the issue
> with Python is resolved (which is either going to happen when 2.5
> comes out, or when the 2.4.3 installer gets updated).
OK, thanks for the help. I guess this is the solution we'll go with for
now
On 28-jun-2006, at 20:56, Bob Ippolito wrote:
>
>
> It's not really trivial, but it's the only option you have unless
> someone else does it first. It sounds like Ronald will probably
> create another 2.4.3 installer in the future that fixes this and a
> few other issues, but I don't know when he
On 28-jun-2006, at 20:50, Michael Glassford wrote:
> Ronald Oussoren wrote:
>> On 28-jun-2006, at 19:02, Michael Glassford wrote:
>>
>>> I've built a universal binary build of an application that runs
>>> great on
>>> the Tiger machines that I've tested it on (both PowerPC and
>>> Intel).
>>>
On Jun 28, 2006, at 11:46 AM, Michael Glassford wrote:
> Bob Ippolito wrote:
>> On Jun 28, 2006, at 10:02 AM, Michael Glassford wrote:
>>> I've built a universal binary build of an application that runs
>>> great on
>>> the Tiger machines that I've tested it on (both PowerPC and
>>> Int
Ronald Oussoren wrote:
> On 28-jun-2006, at 19:02, Michael Glassford wrote:
>
>> I've built a universal binary build of an application that runs
>> great on
>> the Tiger machines that I've tested it on (both PowerPC and
>> Intel).
>> However, when I try to run it on PowerPC 10.3.9 (which I
Bob Ippolito wrote:
> On Jun 28, 2006, at 10:02 AM, Michael Glassford wrote:
>
>> I've built a universal binary build of an application that runs
>> great on
>> the Tiger machines that I've tested it on (both PowerPC and
>> Intel).
>> However, when I try to run it on PowerPC 10.3.9 (which
On 28-jun-2006, at 19:02, Michael Glassford wrote:
> I've built a universal binary build of an application that runs
> great on
> the Tiger machines that I've tested it on (both PowerPC and
> Intel).
> However, when I try to run it on PowerPC 10.3.9 (which I've been
> led to
> believe s
On Jun 28, 2006, at 10:02 AM, Michael Glassford wrote:
> I've built a universal binary build of an application that runs
> great on
> the Tiger machines that I've tested it on (both PowerPC and
> Intel).
> However, when I try to run it on PowerPC 10.3.9 (which I've been
> led to
> belie
I've built a universal binary build of an application that runs great on
the Tiger machines that I've tested it on (both PowerPC and Intel).
However, when I try to run it on PowerPC 10.3.9 (which I've been led to
believe should work from comments in the PyObjC svn log), I get this error:
""
29 matches
Mail list logo
