I'm not sure how the original ones were created to be portable (I think JiHO built them). They certainly don't look portable since some link to dylibs in /opt/local. I may have broken them in that respect when I removed the DYLD_LIBRARY_PATH variable, though they appear to work on Leopard installations fine.[...]
One cause on 10.5.8 is the missing DYLD_LIBRARY_PATH variable in the packages from sf.net!
As I said in a previous message, if I recall correctly, I just compiled the python modules on diverse installations and collected them in the dmg afterwards. I did not do anything special to make them relocatable. So if they don't work now it is probably because of a change in the package and DYLD_LIBRARY_PATH is indeed the likely culprit. However, having it removed was a good change so it would be too bad to have to re-introduce it now... Maybe it would be time to ditch our custom osx-app.sh for something other people already use, e.g. http://sourceforge.net/apps/trac/gtk-osx/wiki/Bundle http://lists.macosforge.org/pipermail/macports-users/2007-February/001727.ht... or other python-based solutions.
JiHO --- http://maururu.net