Comment 3 for bug 932860

I've had a go at a simple conversion based on: http://wiki.debian.org/Multiarch/Implementation - I'm no packaging or multi-arch expert, but I'm learning enough to be dangerous. Please have a look at let me know where it could be improved.

It's was a little more complex than a simple conversion:
* Had to push out the Xsession file to two separate packages (appmenu-gtk-common, appmenu-gtk3-common) and mark Multi-arch: foreign; as this file would conflict if you had both i386 and x86_64 packages installed
* Removed the if statement around the export entry in Xsession file as I don't think this is required(?), if the package is installed, the module should exist - or was this a safety thing? Having the module path means this would be harder to split into -common packages and/or require you to have one per architecture with a different name
* moved debian/appmenu-gtk3.install and debian/appmenu-gtk.install to .in files and manipulate them in debian/rules as they contain arch specific paths that do not get auto generated the way I've seen in other packages with /*/

I'm going to be testing this out, it's currently building in my test ppa: https://launchpad.net/~tellis/+archive/multiarch

Feedback warmly welcome!