Comment 8 for bug 562948

First of all some news for the future: OpenOffice.org 3.3 will finally introduce a system where no registration for plugins are needed, just adding or removing symlinks. Yay for that.

Regarding the option 4): on the upstream voikko mailing list it was proposed that for Debian squeeze one might try and assume that no unopkg compatibility breaking changes would be forthcoming, in which case openoffice.org-voikko's Pre-Depends could be removed and commands in pre* scripts could be moved to post* scripts, resolving the situation (if there are no caveats). However, it has not yet been tested - I prepared such ooo-voikko for testing, but dist-upgrade 5.0 -> 6.0 fails in Debian currently for other reasons.

I think one can conclude that for lucid any big, untested change in openoffice.org-voikko packaging will be a big, untested change. Therefore since we have the update-manager, going with a quirk for it seems most reasonable. On a thought level, it's completely simple:
a) at the beginning of an upgrade from hardy or karmic to lucid, check and remove openoffice.org-voikko
b) at the end of an upgrade, if openoffice.org-voikko was installed before the upgrade, install the new version back.

Since OOo 3.3 will finally solve this probably once and for all, the update-manager quirk should be reasonable. However, while preparing the attached patch, I bumped into some obstacles, partially because not understanding how update-manager works:

problem 1: I don't know how to test update-manager hardy -> lucid with custom update-manager

problem 2: Removing ooo-voikko before installation:
* Since the ooo-voikko problem appears already in the dist-upgrade calculation phase, the ooo-voikko should be removed already before that which on the other hand breaks the idea of not touching anything before starting the installation
* However, if the current markRemove during lucidPostInitialUpdate is enough to fix the calculation without any negative side-effects, that's good

problem 3: Adding ooo-voikko after installation:
* Is markInstall during postUpgrade too late, should one do more like some manual apt-get install?
* Does the markInstall somehow disturb the fact that after it cleanup phase will begin which just removes stuff?