On Wed, Oct 14, 2009 at 13:18, Tim Teulings <r...@edge.ping.de> wrote: > >> * The autobuilder will run maemo-optify after the build, UNLESS a >> control field says not to (or the package already uses /opt). >> This WILL create bugs which package maintainers will need to fix. >> ACTION: mvo to liaise with jeremiah & X-Fade > > Since there currently seem to be problems with maemo-optify we later in the > discussion decided to make it opt-in for around month(!?) to be able to > find bugs in a more controlled environment, then make it opt-out > afterwards.
True, thanks Tim! A bad omission on my part. Obviously there is a transition needed to get from the point we are now (maemo-optify specifically required) to where we want to go (most packages automatically optified) via a testing phase (opting-*in* to automatic optification). Any other corrections? Cheers, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
