[MacPorts] #27828: py26-py2app @0.52 (and py25-py2app) cannot build apps on x86_64

[MacPorts]

#27828: py26-py2app @0.52 (and py25-py2app) cannot build apps on x86_64
--------------------------------+-------------------------------------------
 Reporter:  abarnert@…          |       Owner:  macports-tickets@…                   
     Type:  defect              |      Status:  new                                  
 Priority:  Normal              |   Milestone:                                       
Component:  ports               |     Version:  1.9.2                                
 Keywords:                      |        Port:  py26-py2app py25-py2app              
--------------------------------+-------------------------------------------

Comment(by abarnert@…):

 Replying to [comment:4 jmr@…]:
 > Certainly from my perspective the easiest fix would be for him to
 release a new version. The existence of a patch changes things; if a new
 upstream release is not imminent, I can apply it to the port.

 I have no idea if it's imminent or not. Hopefully he just forgot to upload
 it, and now that he's been reminded it'll be soon, but who knows?

 As for a patch: There seems to be an 0.5.3 tag in the repo, so I guess you
 could diff 0.5.3 against 0.5.2 and use that. Alternatively, just copy the
 8 apptemplate files from the current version over what's included in
 0.5.2, or post-process the apptemplates with lipo. (I tested both, and
 both seem to work.)

 What about just making the port pull the tagged build out of hg instead of
 going to PyPI? It might be less work than building a patch manually. Or is
 that the kind of thing that would warrant a separate py2app-devel port
 and/or be flat-out inappropriate for MacPorts?

 > > Is there some way to disable 0.5.2 for arch combinations that it can't
 handle (basically, anything but fat, fat3, and universal)?
 >
 > Not really. It's dependent on how python is built anyway.

 OK. In this case, the default MacPorts Python (at least on SL/x86_64
 machines) can't use py2app, which is pretty bad. But I wouldn't want you
 to disable the port entirely, especially since I just setup an i386+ppc
 MacPorts tree that I'd like to work. :)

 This isn't too urgent, at least for me; because of two other bugs that
 affect the same projects I wanted to py2app. (One of them is related to
 py2app: if you include most of the Qt4 libraries, or any equivalently-
 large set of stuff, you get a "New Mach-O header is too large to relocate"
 error when trying to py2app a 64-bit binary.) So, I'm backing off 64-bit
 builds for a while.

-- 
Ticket URL: <https://trac.macports.org/ticket/27828#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS