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

[From: Ed Bartosh]

2009/10/28 Andrew Flegg <andrew at bleb.org>:
> Hi,
>
> I've put together a suggested spec for the decision, taken at the
> summit during the /opt BOF[1], that the auto-builder would run some
> maemo-optify version during the build process (controlled by a control
> file header):
>
>    http://talk.maemo.org/showthread.php?p=359996#post359996
>
> I suggest the header is XS-Maemo-Optify, and has the following values:
>
>  none:   no optification should be done, or considered, by the autobuilder.
>  manual: the application author will do optification manually. If the
>          package contains no entries under /opt it would be considered a
>          build failure.
>  auto:   maemo-optify would be run if certain heuristics were met (e.g.
>          no entries in /opt, no Python dependency)
>  force:  maemo-optify would always be run
>
> Marius: are you taking ownership of talking to Ed Bartosh, and anyone
> else, about this plan?
>
We can discuss it here.

Sorry, I seem to miss the whole point of this activity. Why do you
need to do that on autobuilder side? As far as I understood it's just
a matter of including maemo-optify as a build dependency  and run it
in debian/rules, right? Why developer can't do this then? I don't see
much difference between setting XS-Maemo-Optify and changes I
mentioned above. In both cases developer should understand what
optification means.

BTW, when you want to have it done?
I'm going to vacation in a couple of weeks. Before that I was going to
finish implementation of multiple packages builds if I have time.

-- 
BR,
Ed