On Fri, Jan 8, 2010 at 12:55, Anderson Lizardo <[email protected]> wrote: > > It would be nice to have a option to force optification, even if the > heuristics says to ignore the package. I've seen some Python packages > that had no problems with automatic optification, so that way they can > still use maemo-optify.
Marius, how hard would it be to implement the "force" option in debian/optify? This ignores all heuristics and is the exact opposite of "none". > BTW, if/when autobuilder changes to automatically optify packages with > no debian/optify entry, will it be done only for the newer uploaded > packages? I'd argue a rebuild of everything in Extras-testing and Extras into -testing with a suffix of "-autooptify". That'd mean that people can upload still newer versions whilst testing/promoting the auto-optified versions up to Extras. Ideally, any developer who's package gets changed by maemo-optify-deb at this point would receive an email telling them there is a new, auto-optified version in -testing; and how to turn configure the builder through debian/optify. Cheers, Andrew -- Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
