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

From: Ed Bartosh bartosh at gmail.com
Date: Mon Nov 2 17:55:23 EET 2009
2009/11/2 Marius Vollmer <marius.vollmer at nokia.com>:
> ext Graham Cobb <g+770 at cobb.uk.net> writes:
>> On Thursday 29 October 2009 11:12:45 Marius Vollmer wrote:
>>> ext Alberto Mardegan <mardy at users.sourceforge.net> writes:
>>> >>   b) A control file field makes the most sense to
>>> >>      control the build process.
>>> >
>>> > Agreed.
>>> I think dedicated files in debian/ are better, like the
>>> debian/<package>.install files, etc.
>> There is a difference.  A debian/optify is fine for controlling how
>> maemo-optify works.  A control field is more logical for controlling how the
>> auto-builder works: i.e. should it call maemo-optify at all, should it reject
>> the package because it claims to be optified but there are not files in /opt,
>> etc.
> I was thinking that the auto-builder would always calls maemo-optify,
> and maemo-optify would do the rest: decide whether to do anything, check
> for correct optification, etc.
That's the plan so far. autobuilder calls dpkg-buildpackage without
checkiing anything, like it already does.

More information about the maemo-developers mailing list