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

[From: Ed Bartosh]

2009/11/5 Ed Bartosh <bartosh at gmail.com>:
> 2009/11/5 Marius Vollmer <marius.vollmer at nokia.com>:
>> ext Ed Bartosh <bartosh at gmail.com> writes:
>>
>>> 2009/11/5 Marius Vollmer <marius.vollmer at nokia.com>:
>>>
>>>> Then I propose to put maemo-optify into the sdk repo, add a dependency
>>>> to it from build-essential and make a new SDK release.
>>>>
>>>> Whenever we need to update maemo-optify, we need to make a new
>>>> rootstrap.
>>>>
>>> It would take a lot of time, I think.
>>>

I've discussed this with sbdmock author and we decided to make small
change to sbdmock:
New configurable action will be introduced. This action will be
executed by sbdmock between unpacking rootstrap and installing
build-deps.

For Fremantle we can simply put 'apt-get install maemo-optify' in there.

I'll try to make this change on weekends and deploy new sbdmock and
devkit in production.

It would be nice If somebody could explain me what should I expect
from maemo-optify in the following cases:
- source package doesn't contain anything /opt specific, binary
package doesn't contain /opt
- source package doesn't contain debian/optify, binary package doesn't
contain /opt
- source package doesn't contain debian/optify, one binary package
doesn't contain /opt, another binary package does
- source package contains debian/optify, binary package contains /opt
- source package contains debian/optify, one binary package contains
/opt, another binary package doesn't
....

Thanks,

-- 
BR,
Ed