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

[From: Ed Bartosh]

2009/11/6 Marius Vollmer <marius.vollmer at nokia.com>:
> ext Ed Bartosh <bartosh at gmail.com> writes:
>
>> 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.
>
> Excellent, thanks!
>
>> It would be nice If somebody could explain me what should I expect
>> from maemo-optify in the following cases:
>
> Maemo-optify can be invoked in a number of ways.  I'll explain what
> happens when the modified dpkg-buildpackage calls
>
>    maemo-optify-deb --auto
Which is how it's used in modified dpkg-buildpackage, right?

> after running ./debian/rules build.
>
>> - source package doesn't contain anything /opt specific, binary
>>   package doesn't contain /opt
>
> Nothing will be done because debian/optify does not exist, and the
> default mode is "none".
>
So, after deployment nothing should change unless developers add
debian/optify to their packages, right?

When autobuilder expected to start to optify packages without
debian/optify in them?

-- 
BR,
Ed