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

From: Ed Bartosh bartosh at gmail.com
Date: Mon Nov 2 11:13:36 EET 2009
2009/11/2 Andrew Flegg <andrew at bleb.org>:
> Ed wrote:
>> 2009/11/2 Marius Vollmer <marius.vollmer at nokia.com>:
>> > 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.
> This is a problem. We need to be able to iterate maemo-optify to change its behaviour and, at some point, be able to switch its default mode from 'none' (to either 'auto' or 'manual').
OK, we can make dependency from dpkb-buildpackage to maemo-optify not
so strict. If maemo-optify is present it will be called from
With this approach we can put maemo-optify into rootstrap.
BTW, official rootstrap is also part of the SDK releases, so frankly
speaking I don't see much difference between these two options.

> How quickly will we be able to iterate changes to the devkit?
It's just one package, so pretty quickly.

> How happy will the SDK team be to make these changes?
Well, their main goal to support developers, right? I think they will
be extremely happy that someone did almost all job for them.
However, it's better to ask them directly. It's good oportunity to try
to collaborate with them, so we can use it.

> How will devs get new versions in their SDKs (reinstall devkit?!)?

> Depending on these answers, perhaps we should have the maemo-optify package include maemo-buildpackage which is a wrapper around dpkg-buildpackage & maemp-optify.
In this case it has to be included into rootsrap, which is provided by
the same SDK team, so anyway we should work with them somehow.

More information about the maemo-developers mailing list