oh noes!

Debian version 0.9.91.4-1 of nspluginwrapper went into unstable today. Notable changes are:

• Install plugins into /usr/lib/nspluginwrapper/plugins, then symlink them into browser-specific paths. Namely:
  • /usr/lib/firefox/plugins
  • /usr/lib/iceweasel/plugins
  • /usr/lib/mozilla/plugins
  This closes bug #417288.
• Remove the symlinks when symbolic links in the above paths point to the plugin being removed.
• Remove ia64 from the architecture list - there's just no compiler available to build i386 binaries on ia64.
• Set --with-lib32 to /usr/lib32, because otherwise it's assumed to be /usr/lib (which is whatever the "native" architecture is).
• Set --with-lib64 to /usr/lib. Which makes sense if you read the previous bullet point.
• Remove config.sub and config.guess, because the package doesn't use autoconf/automake, and it's just not needed.

I consider the work on the symlinks to be "stable", although I question it's usefulness enough to send it upstream. Ideally, I hope that future Debian browser versions try to keep a single common plugin path. Until then I consider this a temporary measure.

In the meantime, I'm wracking my brains trying to think of some way I can package this for non-amd64 architectures. It would be really useful to see this on PowerPC systems, but the lack of gcc capable of building i386 binaries on anything other than i386 and amd64 means building a cross compiler, libc and Gtk+ libraries prior to the runtime build.

Anyway. Until I work that obstacle out, you amd64 users can enjoy the latest StrongBad E-Mail in Adobe Flash on your Debian boxes.