[maemo-developers] Considering /opt and MyDocs in your packages

[From: Marius Vollmer]

ext Graham Cobb <g+770 at cobb.uk.net> writes:

> On Thursday 10 September 2009 12:16:59 Marius Vollmer wrote:
>
>> Also, you can make it so that maemo-optify only runs in debian/rules
>> when it is present:
>>
>>      which maemo-optify && maemo-optify
>
> Small correction: that doesn't work (because it returns an error status when 
> maemo-optify is not present).

Right, sorry for hastily posting untested code.  (I should know better
not to do that.)

> Is the idea that the autobuilder will automatically install maemo-optify if it 
> exists for that version or do we have to add it to our Build-Depends?

Good question.  I haven't really thought this through, obviously... :-/

Right now I would say that the buildbot should automatically install it,
but maybe that is a bit brittle.

What about uploading a version of maemo-optify to all buildbots, and
only the one in Fremantle does any actual optification?

Or we could do something more general ala the type-handling package in
Debian.  We could have a package that Provides virtual packages like
"fremantle", "not+fremantle", "diablo", "not+diablo" as appropriate for
the distribution it is in, and then packages can have Build-Depends like

    Build-Depends: maemo-optify | not+fremantle

Might be overkill, dunno.