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

[From: Ed Bartosh]

2009/11/2 Marius Vollmer <marius.vollmer at nokia.com>:
> ext Ed Bartosh <bartosh at gmail.com> writes:
>
>> 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.
>
> We should prepare a concrete patch against dpkg-buildpackage, of course.
> I will do that.
>
Please, use dpkg-buildpackage from the current devkit:
http://scratchbox.org/download/files/sbox-releases/stable/src/scratchbox-devkit-debian-1.0.10.tar.gz

> Would maemo-optify be part of that devkit as well, or would it be in the
> rootstrap?
>
> I prefer to leave maemo-optify in the rootstrap: that way, we can update
> it much easier, which is quite important at this stage.
>
Unfortunately it has to be part of the devkit. Otherwise it will
behave differently with different rootstraps and make devkit
inconsistent.

>> - 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
>
> If someone is willing and able to keep a close eye on the buildbot, then
> we could deploy the devkit in the buildbot quite early.  It might break
> some builds, but if we are able to react quickly, then it is better to
> catch those broken builds earlier than later.  Ed?
>
Of course I'll take care of this. I can also help with building devkit
if needed.

What's the best way to make SDK guys to adopt our changes? Bug?

-- 
BR,
Ed