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

[From: Thomas Perl]

2009/10/15 Quim Gil <quim.gil at nokia.com>:
> ext Thomas Perl wrote:
>> In the latest version of gPodder (written in Python), I have started
>> using maemo-optify. It saves around 1 MB according to maemo-optify's
>> output. The problem is that now when a user upgrades from an older
>> version to this version, it breaks (the user cannot start the
>> application from the icon, and starting it from the command line tells
>> me that Python can't find the "gpodder" module).
>>
>> 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 :/
>
> "lots of users" before sales start = actually not that many and all of
> them quite savvy and even probably reflashing at this point.
>
> Thanks for you report though. It's clearer that unless we find several
> solutions the time for optification is NOW, or whenever a developer is
> pushing a first release to Extras.

Feel free to test the newer version and rate/comment on the package here:

http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/gpodder/2.0+git20091013-thp1/

The non-optified version from September is already in Extras, and it
would be nice to get this updated, optified package into Extras before
sales start to avoid having clueless users think that the app is broken :)

Thanks,
Thomas