[oe] [RFC] policy about nonworking recipes
Rolf Leggewie
no2spam at nospam.arcornews.de
Thu May 21 20:20:30 UTC 2009
Hi,
we have recipes/nonworking/ to collect known-to-be-broken recipes. With
the explosion of MACHINE, DISTRO and other settings, most all recipes
are prone to fail in some circumstances. Occasionally, this has led to
packages being moved to nonworking that were only broken for some
occasions and possibly essential for others. Problems reported in the
bug tracker had not always gotten on the radar of the person needing the
recipe. The result is frustration left and right.
We already have COMPATIBLE_MACHINE and COMPATIBLE_HOST, but they're not
commonly used. As a matter of policy, I think we should agree on
setting COMPATIBLE_MACHINE to an empty string for packages that fail in
do_configure or do_compile and which otherwise would have been a
candidate for recipes/nonworking. The recipe will then not be
considered by the parser.
The person who wants the recipe finds it right where he would expect it
and can add a regexp for the MACHINE he knows this recipes is working
for. Furthermore, "git log" can't track moving operations very well and
this proposal avoids renaming files.
I think that, eventually, "bitbake world" should be working again and
usable as a test case. I suggest to use COMPATIBLE_MACHINE because I
assume that to be the more common issue.
Best regards
Rolf
More information about the Openembedded-devel
mailing list