OE-lite Terminology

OE-lite manifest
A git repository used as top-level for the project, containing as a minimum the definition of OE-lite stack used in the project (the conf/bakery.conf file). It typically also contains other project specific parts, such as project specific configuration files, and OE-lite recipes, scripts and documentation.
OE-lite stack
An ordered list of OE-lite layers, and various properties assigned to these.
OE-lite layer
A subdirectory of the OE-lite manifest, holding either OE-lite metadata or Python library code. An OE-lite layer is typically contained in its own git repository.
OE-lite layer, external layer
An OE-lite layer hosted in a git repository not related to the projects OE-lite repository. When creating clones of the OE-lite repository, the layer will be cloned from the (external) git repository. Using OE-lite/core directly from git://oe-lite.org/oe-lite/core.git is an example of an external layer.
OE-lite layer, internal layer
An OE-lite layer hosted in a git repository which is placed under the manifest repository using the same relative path as is used in the OE-lite stack, and is referenced in the OE-lite manifest using relative paths. An example of an internal layer is an OE-lite project with the manifest repository hosted at git://oe-lite.org/bsp/foobar.git has an OE-lite/core layer at meta/core hosted at git://oe-lite.org/bsp/foobar.git/meta/core, and referenced in the manifest using the url ./meta/core .
OE-lite layer, embedded layer
An OE-lite layer contained directly in the OE-lite manifest repository, and is as such indivisible from the manifest. This should normally only be used for layers that has no re-use potential for other projects, now and in the future. The top of the OE-lite manifest is always treated as an implicit embedded layer. Other than this implicit top-level embedded layer, this layer type is not advisable.
OE-lite repository
A bare clone of the OE-lite manifest git repository, and bare clones of any OE-lite layers using relative paths.
OE-lite class
A file providing certain functionality to recipes, allowing one to avoid duplicating logic and simplify recipe files.
OE-lite recipe
A recipe describes how to build a piece of software. The output of a recipe is one or more packages. For example, a recipe for a library would typically be split into a package containing the library itself, a -dev package containing the header files, a -dbg package containing the debug symbols and possibly a -doc package containing documentation.
OE-lite package
A package is a tar-ball containing a subset of the files produced from a specific recipe. A package provides one or more items.
OE-lite task
A task is one step in the building of a recipe.
OE-lite item
An item is the fundamental unit which is used for resolving dependencies.
A package which is used to satisfy dependencies without building it ourselves.
ingredients directory
A directory, usually just named ingredients and located in the OE-lite manifest directory, acting as a local cache for fetched source tar-balls.
The process of populating the ${WORKDIR}/stage directory with all utilities, libraries and other files necessary to build a given recipe.