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

From: Graham Cobb g+770 at cobb.uk.net
Date: Thu Oct 29 14:14:51 EET 2009
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.  If you are doing your own optification you shouldn't need a 
debian/optify - just a control file field to tell the autobuilder not to run 
maemo-optify at all.

So, I would not see the things Andrew defined going in to debian/optify.  But 
debian/optify would be a good place to put things like: what is the size 
threshold for optification, what directories should be optified as a whole 
directory, which files/directories should be left untouched, etc.

More information about the maemo-developers mailing list