New optification issues in extras-testing

[Attila Csipa]

On Tuesday 29 December 2009 14:01:40 Till Harbaum / Lists wrote:
> This rule that the sum of all components also has to stay below a certain
> limit is new. Osm2go is below 500k and so is the goocanvas it depends on.
> Now this guy is talking about the fact that the sum is over 500k.

Any limit that includes dependencies will simply not work as there is no 
guarantee (except with the rare exception where the developer is maintainer of 
ALL the dependencies as well) what amount of space will be used on the NAND. 
Different versions might have different optification rules, they might grow or 
shrink, include additional dependencies of their own, etc. 

A source of misunderstanding might be the wording of the requirement: The 
application or its dependencies ignore the recommendation to use the eMMC to 
install as much files as possible, filling the root partition with 500kb or 
more. 

I can see how this can be interpreted both ways - both total and per package. 
As IMHO there is no point in the former (see above), and if there is a 
consensus about this it should perhaps be corrected that the per-package 
context of the 500K is clear(er).

A broader question is if the 500K as a *number* should be part of the blocker 
paragraph. AFAIK the 500K is a guideline (unless 'encouraged' became a synonym 
with 'required'), what we are (supposed to  be ?) looking at here is the 
general principle of avoiding *unnecessarily* wasting resources.

Regards,
Attila