Ed wrote: > 2009/11/2 Marius Vollmer <marius.voll...@nokia.com>: > > > Would maemo-optify be part of that devkit as well, or would it be in the > > rootstrap? > > > > I prefer to leave maemo-optify in the rootstrap: that way, we can update > > it much easier, which is quite important at this stage. > > > Unfortunately it has to be part of the devkit.
This is a problem. We need to be able to iterate maemo-optify to change its behaviour and, at some point, be able to switch its default mode from 'none' (to either 'auto' or 'manual'). How quickly will we be able to iterate changes to the devkit? How happy will the SDK team be to make these changes? How will devs get new versions in their SDKs (reinstall devkit?!)? Depending on these answers, perhaps we should have the maemo-optify package include maemo-buildpackage which is a wrapper around dpkg-buildpackage & maemp-optify. 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
