Comment 31 for bug 202174

Right now an issue is coming up with a compile-time-only dependency on a libasio-dev, which is just a collection of header files. Unfortunately, Ubuntu has this in Universe, and so to stay in Main and enable collaboration support (which requires this) is a bit complicated. The options are:
1 - MIR libasio-dev (It has been reviewed by the boost c++ folks and will be included in a future version there, so I'm assured it is safe, and I know it is useful.) This is probably ideal.
2 - Include an abiword-specific copy as a patch. Not ideal from the standpoint of code duplication, but I am used to tracking upstream deps closely, I must do the same for the Windows build. This might be the easiest - I already have a package (soon to hit the PPA) that should enable this solution.
3 - Disable collaboration. This is really not ideal, as Ubuntu would be missing out on a major advancement. This does leave open the option of re-packaging abiword-plugins-universe, but I'd argue this is even uglier than #1
4 - Demote AbiWord from Main to Universe. I am against this idea right now, due to the lost exposure (we have the top spot on a default open of Add/Remove... in Hardy, with 4 nice stars next to us) and perhaps the ambiguous statement changing "Supported Applications" to "All Applications" would make about AbiWord's viability (of course AbiWord is supported, as in not unmaintained, it's just that universe doesn't receive canonical's backing I believe).

As it stands, I am in favor of #2 while I pursue #1 (the presumably "right way" to do things). The package 2.6.2-0ubuntu0~ppa8 is building right now, and should resolve all the concerns I presently have with the package (implementing #2, and fixing the abiword-extras issue I had earlier). Please review this package at your convenience - I will go through the Sponsorship information later tonight or tomorrow.

The packages are at https://launchpad.net/~cezpi4y02/+archive