Poky contains a great amount of metadata as machine definition files, classes, and recipes that cover everything from simple applications to full graphical stacks and frameworks. The main motivation to use layers is to organize the long list of providers better and still make sure users may be able to pick only the needed or desired provider. It is also a way to provide a customizable source code that can be used for any architecture or modified in the way the user needs.
We can choose the set of layers needed for each project. We can configure the provided source code for our needs because we want to configure how one package acts in our product or because we want the package built with our architecture flags. This means that using layers, we can provide additional features to Poky (represented by recipes from additional layers) that may be modified according to our needs (represented by the configuration appends we include for external recipes).
In addition...
