Re: [PATCH 2/2] recipes: Update recipes to get 'bitbake world' parse and calculate runqueue successfully.

[Mike Westerhof <mike@mwester.net>]

Frans Meulenbroeks wrote:
> Koen brought up this in the thread on the review process. As it
> (mostly) is about this thread I felt it was more appropriate here.
[snip]
> I don't know what others think about it, but I see only a few matches.
[snip]
> PS: I think this is also an excellent case why it is a good idea to
> identify the maintainer within the recipe/

I think this gets at the heart of why Frans' recent changes make *me*
uncomfortable -- their scope is broad and the general approach by Frans
is to make everyone else provide detailed and precise arguments
defending why the broad change should not apply to specific items.

I, for one, would like to understand where this "cleanup" effort is
ultimately going to go.  What distros will ultimately remain in OE?
What what will be the final criteria for recipes being permitted to
remain in OE (it seems to be converging on "it must build with bitbake
world, despite the many emails that have offered sound reasons for why
that is a poor test of recipe quality (which begs the question of why
recipe buildability might be a valid measure of quality in the first
place)).

Most of the patches and changes in OE have very specific distros in
mind, or they set out to solve reasonably bounded problems when they
cross distro boundaries.  Frans' changes do not.  The result is that
each and every of these patches must be carefully reviewed.  I asked a
specific question of Frans earlier that he did not answer, for whatever
reason.  I'll ask again: What distros does Frans test to ensure that his
patches are sane?

It's great that we "clean up" OE, but in my opinion, it's being done
with a sledgehammer approach, and I for one find it uncomfortable being
"threatened" by the creator of these global giant patches setting
policies about same that require the community to carefully defend their
work or interests, or else.

C'mon folks -- I'm not the only one who's busy, and who's uncomfortable
with this.  Dev branch or not, this is NOT the way to get a community
working together.

-Mike (mwester)