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

From: Andrew Flegg andrew at bleb.org
Date: Thu Oct 15 15:16:30 EEST 2009
On Thu, Oct 15, 2009 at 11:21, Thomas Perl <th.perl at gmail.com> wrote:
>
> Is it possible to fix that problem somehow? Or should I just disable
> optification?

Would "Conflicts: gpodder (< 1.0.0)" work? If not, could it be done
through a double step? For example:

    gpodder     0.9.0 (existing on device)
    gpodder     1.0.0 (depends: gpodder-opt)
    gpodder-opt 1.0.0 (conflicts: gpodder < 1.0.0)

Debian & App Manager experts (or someone with time to test) needed to
answer that (Jeremiah/Marius?)

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

The conclusion from the BOF was that ultimately /opt would be
considered a SHOULD requirement for Extras for pretty much everything.
An application author should have very good reason for not using it
(similar to having a finger-friendly UI)

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/
More information about the maemo-developers mailing list