New optification issues in extras-testing

[Andrew Flegg]

On Tue, Dec 29, 2009 at 13:01, Till Harbaum / Lists <lists at harbaum.org> wrote:
>
> the page you are referring to says:
>
> "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. "
>
> It does not say that the _sum_ of all dependencies has to be below 500k.

I agree, it looks ambiguous. The *intent* seems to be that installing
an application shouldn't take up more than 500KB of the rootfs (your
Python example on the package page is specious, BTW, as Python is now
optified).

If the dependencies are used by lots of apps, and have separate
maintainers; I can understand your point. However, since:

  * you maintain both libgoocanvas3 and osm2go
  * neither are optified (according to the comments)
  * I *imagine* there aren't lots of other apps depending on
    libgoocanvas3 which have been let through QA

...this would seem to fall on to your shoulders. The STRONG
recommendation is that EVERYTHING is optified, and getting pedantic
about the numbers when you control both halves of the application
stack seems a little churlish. After all, someone wanting to be
difficult could split their app into 500 2KB packages which depend on
each other :-)

Now, on to solving the problem, have you tried putting "auto" in
debian/optify? If so, did both packages continue to work after being
auto-optified by the builder (or maemo-build-deb in Scratchbox, if you
prefer).

The intention is that they *should* (which is why 'auto' will become
the default at some point in the future).

Hope that helps,

Andrew

-- 
Andrew Flegg -- mailto:andrew at bleb.org  |  http://www.bleb.org/