overview-manual: provide a more expansive definition of "layer"

A layer is not simply a collection of recipes; it can include any
combination of recipe files, machine and distro configuration files,
class file and more, so make that clear. In fact, a layer is not
required to contain any recipe files at all.

(From yocto-docs rev: 4050b1002e1d1273fb3e0908bd42308e4f95e355)

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
(cherry picked from commit 9d2fe509ff2ab43ea73d6cb7feaa44669ad83f0d)
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Paul Barker <paul@pbarker.dev>
This commit is contained in:
Robert P. J. Day
2026-06-03 10:11:53 -04:00
committed by Paul Barker
parent bee8b23299
commit da03ea708b

View File

@@ -781,7 +781,9 @@ helpful for getting started:
their code available to other application developers. For information
on the eSDK, see the :doc:`/sdk-manual/index` manual.
- *Layer:* A collection of related recipes. Layers allow you to
- *Layer:* A collection of related metadata, which could include any of
recipes, machine configuration files, distro configuration files
and/or class files. Layers allow you to
consolidate related metadata to customize your build. Layers also
isolate information used when building for multiple architectures.
Layers are hierarchical in their ability to override previous