The information in section **3.3.8 Licensing** (https://docs.yoctoproject.org/dev-manual/common-tasks.html#licensing) and under https://docs.yoctoproject.org/ref-manual/variables.html#term-LIC_FILES_CHKSUM is well-written and much more clear than the 2.x documentation that keeps coming up with Google searches.

One thing that is not clear is how to differentiate the license terms that apply to the layer, its recipes and configuration files versus the license terms that apply to the component(s) that results from incorporating the layer.

For example, assume the license I wish to apply to the layer (scripts, config files, etc.) is "MIT" but the result of applying that layer is a collection of libraries to which the "GPLv3" license is applied. Are there guidelines that need to be followed regarding the license terms for the layer, its recipes and its configuration files? Is there an accepted practice for this that needs to be stated in the documentation?

I hope this is making sense. The issue is making sure that it is clear that the license terms for the layer and its scripts and config files are independent of the license terms that apply to the net result of applying that recipe.