[oe] Kernel recipes with broken PRs now

[Phil Blundell]

On Sun, 2009-05-24 at 10:23 +0200, Koen Kooi wrote:
> Now, if people posting in this thread would bother to read the original 
> RFC (that got approved for .dev as well as stable/2009), we wouldn't be 
> having this discussion.

I guess the RFC in question is this one:

http://projects.linuxtogo.org/pipermail/openembedded-devel/2009-April/009578.html

but it doesn't seem to really address the issues that have been raised
in this thread.  Indeed, looking at the responses that were posted to
the original RFC it doesn't seem at all obvious that there was a
consensus in favour of the patch; Otavio Salvador said that he was
"fully support[ive]" of it, but everybody else who posted seemed to have
some or other reservations.

If you do want to keep this mechanism then an easy way to make it less
intrusive would be simply to have it be a DISTRO opt-in rather than
standard behaviour.  Then, the distros that want it can be responsible
for making sure that all their kernels have been made compatible with
the patch, and other users don't need to worry about it.  This seems
particularly pertinent for the stable branch where, as I understood it,
intrusive changes were supposed to be avoided.

Per my previous email, though, I think there are probably better ways of
solving the original problem that don't require this kind of global
variable in the first place, and could at least be made to fail in a
"safe" way for users who aren't aware of the change.

p.