[maemo-developers] maemo-optify, autobuilder & /opt

From: Ed Bartosh bartosh at gmail.com
Date: Sun Nov 1 11:02:34 EET 2009
2009/10/29 Graham Cobb <g+770 at cobb.uk.net>:
> On Wednesday 28 October 2009 22:50:25 Ed Bartosh wrote:
>> Somehow I don't like the idea of doing anything with the package
>> without developer being aware of this. I'd rather implement check on
>> autobuilder side to insure that packages are optified. Developer can
>> use option XS-Maemo-Optify: none to disable optification if developer
>> doesn't want it.
> Nobody likes doing something to the package automatically but, after a long
> discussion at the BOF, we agreed that the alternatives were even worse [1].
> In particular, there was a strong argument that the package should not have to
> include anything (even a control field option) to cause optification to
> happen.  Packages which wanted to do their own optification or which had to
> disable optification would have to include an option to stop optification.
> If it makes you happier: rename the autobuilder as "autobuilder and optifier"!
> We did agree that there had to be a way for developers to generate packages in
> the scratchbox environment which had been optified in exactly the same way
> the autobuilder would.  And that we would update the wiki pages about
> checking packages will build to include using that tool to test the
> optification.
> So, the consensus decision was that the solution would be that autobuilder
> should automatically optify by default.

So, what should we do?

My proposal is to make dpkg-buildpackage to call maemo-optify. With
this we can solve 2 problems - autobuilder will optify packages and
developers will have their packages automatically optified for their
local builds without using any extra tools.

More information about the maemo-developers mailing list