[bitbake-devel] [PATCH] bitbake: add event masks

[Richard Purdie]

On Fri, 2013-05-31 at 09:51 -0700, Chris Larson wrote:
> On Fri, May 31, 2013 at 7:19 AM, Bogdan Marinescu
> <bogdan.a.marinescu at intel.com> wrote:
>         Add more arguments to an "addhandler" command. Each argument
>         (after the
>         first one, which is the name of the handler) is the name of an
>         event class
>         that the handler wants to be notified on. "*" is a shortcut
>         for "listen
>         to all events". This changes the current behaviour of bitbake,
>         which is
>         to broadcast all events to all listeners; instead, only the
>         handlers
>         that registered themselves to an event with "addhandler" will
>         receive
>         that event. This should improve performance, although only
>         performance
>         measurements will be confirm or deny this claim.
>         This is part of the fix for YOCTO #3812, but implements
>         filtering only
>         for class event handlers; the other part (events filter for
>         UIs) will be
>         the subject of a different patch.
>         
>         Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu at intel.com>
> 
> Wouldn't it be simpler, as well as less invasive to the file format,
> to add an 'event' or 'events' flag to the handler which indicates what
> events it wishes to handle?

Agreed, FWIW I reworked this and merged it. Since we were messing around
with the bitbake minimum version in OE anyway, it seemed a good
opportunity.

Cheers,

Richard