[oe] [PATCH (resend)] image.bbclass: implement IMAGE_FEATURES

[Chris Larson]

On Tue, Aug 3, 2010 at 6:45 PM, Chris Larson <clarson at kergoth.com> wrote:

>
>
> On Tue, Aug 3, 2010 at 6:40 PM, Chris Larson <clarson at kergoth.com> wrote:
>
>> From: Christopher Larson <clarson at mvista.com>
>>
>> This adds the ability to include groups of packages in an image.  It is
>> similar in concept to the IMAGE_FEATURES used in Poky, but here we use
>> IMAGE_FEATURE_<feature> and IMAGE_FEATURE_<feature>_OPTIONAL, rather than
>> base_contains calls.
>>
>> Initially defined groups:
>> base - the packages requested via IMAGE_INSTALL & IMAGE_BOOT
>> dbg - debug packages
>> dev - development packages
>> doc - documentation packages (of limited use at the moment due to
>> task.bbclass)
>> vmlinux - kernel debugging packages (just kernel-vmlinux at the moment)
>>
>> To add groups to your images:
>> IMAGE_FEATURES += "dbg dev"
>>
>> To add a new package group:
>> IMAGE_FEATURE_myfeature = "gstreamer python pulseaudio"
>>
>
> Note that using package_dbg.bbclass can be useful when using the "dbg"
> group/feature, as it switches to using one -dbg package per binary package,
> rather than per recipe.  INHERIT += "package_dbg".
>

Hmm, IMAGE_FEATURES is consistent, but conceptually this is more an
implementation of 'package groups' for root filesystem population than
anything to do with the "image" creation process.  Anyone have any
suggestions on better names for the variables?
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics