Comment 4 for bug 738947

-Why ige-mac-bundle?
The main reason for suggesting this approach is that it lowers the amount of code to be maintained under Inkscape (to the risk of increasing its dependency on others). In the longer term, jhbuild could be used instead of MacPorts. In my case, I already need a MacPorts tree. Maybe using the tools that others have developed for the very purpose of integrating GTK+ application with OS X is a valid reason. Before that, and hopefully, something good will come from the -headerpad_max_install_names discussion at MacPorts, so that the custom MacPorts step is not needed anymore.

-Python?
I imagine python can be built under MacPorts and then included by ige-mac-bundler. What to include in the app can be fine tuned by ige-mac-bundler.

-Universal packages?
That I don't quite know. It looks like a build per arch might be needed. GnuCash provides packages that way, using ige-mac-bundler.

-Snow Leopard requirement?
No requirement for the ige-mac-bundler part. For ige-mac-integration, some aspects are x86_64, some are not.

By the way, I have started experimenting with the menu bar integration provided by ige-mac-integration. It looks like Inkscape does not use GtkUIManager for its menus. It seems to be an issue.