[maemo-developers] maemo-optify, autobuilder & /opt
From: Marius Vollmer marius.vollmer at nokia.comDate: Mon Nov 9 09:01:14 EET 2009
- Previous message: maemo-optify, autobuilder & /opt
- Next message: maemo-optify, autobuilder & /opt
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ext Ed Bartosh <bartosh at gmail.com> writes: >> Maemo-optify can be invoked in a number of ways. I'll explain what >> happens when the modified dpkg-buildpackage calls >> >> maemo-optify-deb --auto > > Which is how it's used in modified dpkg-buildpackage, right? Correct. >> after running ./debian/rules build. >> >>> - source package doesn't contain anything /opt specific, binary >>> package doesn't contain /opt >> >> Nothing will be done because debian/optify does not exist, and the >> default mode is "none". > > So, after deployment nothing should change unless developers add > debian/optify to their packages, right? Correct. > When autobuilder expected to start to optify packages without > debian/optify in them? I don't know. We certainly need to tune the heuristic of maemo-optify first to handle Python.
- Previous message: maemo-optify, autobuilder & /opt
- Next message: maemo-optify, autobuilder & /opt
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]