[maemo-developers] maemo-optify, autobuilder & /opt
From: Ed Bartosh bartosh at gmail.comDate: Thu Oct 29 14:23:01 EET 2009
- Previous message: maemo-optify, autobuilder & /opt
- Next message: Maemo5 MicroB: javascript API for fullscreen, location, cursor enable?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2009/10/29 Marius Vollmer <marius.vollmer at nokia.com>: > ext Andrew Flegg <andrew at bleb.org> writes: > >> I suggest the header is XS-Maemo-Optify, and has the following values: >> >> none: no optification should be done, or considered, by the autobuilder. >> manual: the application author will do optification manually. If the >> package contains no entries under /opt it would be considered a >> build failure. >> auto: maemo-optify would be run if certain heuristics were met (e.g. >> no entries in /opt, no Python dependency) >> force: maemo-optify would always be run > > Thanks for the initiative, Andrew! > > I have put maemo-optify 0.2 into extras-devel with the following > changes, motivated by your proposal: > > * Added --auto option to maemo-optify-deb which will read debian/optify > and debian/files and does the right thing. > > * Added maemo-optify-buildpackage, which invokes maemo-optify-deb in > auto mode. > > More details in the README here: > > http://maemo.gitorious.org/maemo-af/maemo-optify/blobs/master/README > > Thus, only "none" and "auto" are really implemented right now, and the > mode is read from debian/optify instead of from debian/control. > > (Proper man pages are still missing.) > > Thus, the next step is to make sure that maemo-optify is installed in > the build environment and to use maemo-optify-buildpackage instead of > dpkg-buildpackage. (Or make the equivalent changes to dpkg-buildpackage > itself, which are quite small.) > There are two ways to have maemo-optify in build environment - to add it to the rootstrap and to put it into Build-Depends. As I understood we don't want to ask developers to put it into Build-Depends, so rootstrap should be changed. I already hacked it one time when I removed /opt from there. I can do it again, but I don't want to fork SDK rootstrap, so it would be nice to somehow agree with SDK team to include these changes into the next release. I like the idea of making equivalent changes to dpkg-buildpackage. Why we should introduce new tool? -- BR, Ed
- Previous message: maemo-optify, autobuilder & /opt
- Next message: Maemo5 MicroB: javascript API for fullscreen, location, cursor enable?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]