[Pythonmac-SIG] bundlebuilder bug?

[Russell E. Owen]

I just submitted this to sourceforge, but thought I'd see if anybody had 
any suggested workarounds. I'm also unclear if I should be reporting a 
2nd bug as well.

The bundlebuilder command-line argument --lib is supposed to be able to 
include frameworks in the resulting Mac application package. 
Unfortunately, the aliases in the resulting framework copy are all 
broken.

For an example of this, use --lib to include Tcl.framework and then look 
through the framework in the resulting application package. Frameworks 
normally have quite a few handy aliases (such as .../Versions/Current) 
and all the aliases I tried were broken.

I'm not entirely sure if this actually breaks anything. The one app I've 
managed to build with standalone=True and use of --lib to include the Tk 
and Tcl frameworks runs fine on my Mac (which has Python, Tcl and Tk 
frameworks installed) but fails with "True undefined" on another Mac 
running Jaguar that I happened to have handy.

This 2nd problem may be a separate bug or user error on my part. I'm not 
yet sure. 

-- Russell

P.S. I finally got my extra files properly installed by adding to the 
bundlebuilder script such that it:
- unpacks Modules.zip
- copies the two packages in question (overwriting the incomplete 
versions that were already installed; I plan to try excluding them and 
leaving Modules.zip alone).
The results work on my machine but break on a Jaguar machine is noted 
above with True undefined -- as if it's running the python on that 
machine instead of the framework python that's in the application 
package.