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

[From: Marius Gedminas]

On Thu, Oct 15, 2009 at 12:21:54PM +0200, 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).

That's a packaging bug, from the user's perspective.

> 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?

> Another problem is the slower startup speed, which is really
> noticeable now. That's another reason why I would like to go without
> optification.

Ouch.

Have you done any measurements?

Marius Gedminas
-- 
Bumper sticker: No radio - Already stolen.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.maemo.org/pipermail/maemo-developers/attachments/20091015/296f1399/attachment.pgp