[maemo-developers] Optification breaks package on upgrade from non-optified older version

[From: Marius Vollmer]

ext Marius Gedminas <marius at pov.lt> writes:

>> Uninstalling and re-installing the package fixes this problem, but I
>> assume there will be lots of users upgrading from the current version
>> in Extras (non-optified) to some optified version in the future, and
>> they won't just try to uninstall and re-install it and assume that the
>> application is at fault :/
>>
>> Is it possible to fix that problem somehow? Or should I just disable
>> optification?
>
> What's the practical difference between upgrading and
> removing-then-reinstalling?  (It probably shows that I haven't read the
> "maemo-optify and python apps" thread.)  Maybe you could fix the upgrade
> problem by writing a suitable preinst script?

I will have a close look at this soonish.  Right now I assume that we
need to 'fix' dpkg somehow to get over this, but hopefully not.

In any case having upgrades break because of maemo-optify is of course
quite severe and I/we need to fix this 'asap'.