Layer model doomed, unless we all work together

[Philip Balister <philip@balister.org>]

As evidence, please review this list:

http://layers.openembedded.org/layerindex/branch/master/duplicates/

I mean FOUR recipes for alsa-plugins?

I am trying to fix the pyqt recipe in meta-oe, and had th eidea to check
for it in other layers. This leads me to meta-ivi-demo, which has an
update for sip-native and another pyqt recipe. To be fair, they are
using Qt5, so it is a little more complex.

At any rate, we need to stop ripping recipes out of layers and maing
local copies, or worse, updating our local copies and not the primary
layer. The intent of the layer concept was not to fragment development
across many separate repositories.

I see a couple of issues we need to start talking about:

1) recipes that need to move closer to core because a range of other
packages use them.

2) people feel they have to remove recipes from layers and make local
copies.

And just so people know what seriously pisses me off :) Copying a recipe
from a layer, updating it, and not sending the recipe to the layer they
got the update from.

Thanks for letting me vent,

Philip