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

From: Jeremiah Foster jeremiah at jeremiahfoster.com
Date: Mon Nov 2 01:24:47 EET 2009
On Nov 1, 2009, at 18:17, Ed Bartosh wrote:

> 2009/11/1 Graham Cobb <g+770 at cobb.uk.net>:
>> On Sunday 01 November 2009 09:02:34 Ed Bartosh wrote:
>>> 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.
>> I am happy to go with your recommendation.  I guess there is a  
>> small downside
>> that we are forking dpkg-buildpackage but, as you say, the  
>> advantage is that
>> developers will not have to do anything locally.
> So, I can see this way of implementing this:
> - give optification scripts to SDK developers and ask them to prepare
> Debian devkit for Fremantle with patched dpkg-buildpackage as fast as
> possible.
> - test new devkit with local builds and with autobuilder when it's  
> ready.
> - distirbute devkit among developers and change SDK documentation  
> for Fremantle.
> - deploy in autobuilder production
> Any ideas, objections, clarifications?

dpkg-buildpackage is written in perl. It would facilitate merging with  
upstream and any potential downstream if we kept any additional dpkg- 
buildpackage calls/methods as perl modules.


More information about the maemo-developers mailing list