[maemo-developers] Optification breaks package on upgrade from non-optified older version
From: Andrew Flegg andrew at bleb.orgDate: Thu Oct 15 15:07:21 EEST 2009
- Previous message: Optification breaks package on upgrade from non-optified older version
- Next message: Optification breaks package on upgrade from non-optified older version
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Oct 15, 2009 at 12:20, Attila Csipa <maemo at csipa.in.rs> wrote: > > From what I heard that was also the reason why python (and Qt) are/were not > optified, but apparently a choice will have to be made - speed or > application space, but while speed is a 'should', application space is a > 'must'. Correct. > I wonder if some sort of optification could be done on the device itself, > as in make it optional or a choice - this stuff I use often and I don't > want it optified, while somehing else used rarely can be on /opt so it > would not take up space on /. This was discussed in the /opt BOF at the summit. The conclusions here were: * Files accessed regularly by *other* processes (such as .desktop, .service and icons) SHOULD NOT be in /opt. * Every application SHOULD be in /opt. * Doing this on device (with the current approach) would slow down application installation too much, and make debugging in Scratchbox too hard. HTH, Andrew -- Andrew Flegg -- mailto:andrew at bleb.org | http://www.bleb.org/
- Previous message: Optification breaks package on upgrade from non-optified older version
- Next message: Optification breaks package on upgrade from non-optified older version
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]