[bitbake-devel] [PATCH] knotty: Fold knotty2 into knotty and make it the default

[Chris Larson]

On Wed, Aug 15, 2012 at 9:50 AM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> There is no good reason knotty2 shouldn't be the default now. If you need
> the old behaviour, just pipe the output through cat as non-interactive
> terminals get the old output.
>
> Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>

I'm 100% in favor of this series, for what it's worth. I've been using
knotty2 as my default BITBAKE_UI for months, just ignoring the minor
bugs. The reduction in unnecessary output makes it *much* easier to
spot *real* problems.

That said, I think we should look into prefixing some of our log
messages — some of them don't make it clear what task/recipe emitted
them, making it difficult to isolate their cause. But of course, that
was an issue with knotty as well, but it was slightly easier to narrow
down the cause based on where it stood between the task
started/completed messages :). Would you be open to potentially
injecting a log message filter which adds task context informastion,
in the code which forks the tasks? Then the formatter would have to do
a hasattr() to check for that and add it to the format, but it'd mean
we *always* know what task log messages are coming from.
-- 
Christopher Larson