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

From: Graham Cobb g+770 at cobb.uk.net
Date: Thu Oct 29 01:42:55 EET 2009
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 

So, the consensus decision was that the solution would be that autobuilder 
should automatically optify by default.


[1] It reminds me of the famous quote from Winston Churchill: "Democracy is 
the worst form of government, except for all those other forms that have been 
tried from time to time."
More information about the maemo-developers mailing list