Re: [Pyobjc-dev] py2app builds fail leopard codesign integrity checks
Brought to you by:
ronaldoussoren
From: Ronald O. <ron...@ma...> - 2007-11-20 18:59:05
|
On 20 Nov, 2007, at 19:30, Kevin Walzer wrote: > Ronald Oussoren wrote: >> Py2app isn't signing code. The problem is that the py2app >> executable stub inside the py2app package is signed by Apple (it >> isn't signed in the repository). >> I don't know how to remove that signature, but you can download the >> stub executable from pyobjc's repository (downloading from https://svn.red-bean.com/pyobjc/branches/pyobjc2/py2app/py2app/apptemplate/prebuilt/main >> might work for that) > > I don't quite understand the problem here, but do these issues mean > it's a Bad Idea to use the Apple-shipped py2app and PyObjC? I was > planning on doing this when I upgraded to Leopard. Apple-shipped PyObjC and py2app are good enough. The issue with py2app is pretty small, and can be worked around by replacing two files in the py2app package. There are also a number of small bugs in the pyobjc-core package, but nothing major. I will provide update packages some time in the future, but I have no idea when that will be. Ronald > > > --Kevin > -- > Kevin Walzer > Code by Kevin > http://www.codebykevin.com |