2841449527
When a LayerBranch (a specific layer at a specific release) does not
exist in the layerindex database ("Layerindex Metadata"), the dependency
would throw a backtrace. Instead fail early and provide an error message.
Since layerindexlib will also check the local layers, inform the user that
a local checkout might resolve the situation. Recommend that they reach
out to the layer maintainers and layer index admins to properly fix it for
everyone.
While we are here, remove some trailing whitespace.
[YOCTO #15365]
[YOCTO #13954]
(Bitbake rev: 96cbe8f87209a927c157ebcf469f8b9d54fcf92e)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
||
|---|---|---|
| .. | ||
| tests | ||
| __init__.py | ||
| cooker.py | ||
| plugin.py | ||
| README | ||
| restapi.py | ||
The layerindexlib module is designed to permit programs to work directly with layer index information. (See layers.openembedded.org...)
The layerindexlib module includes a plugin interface that is used to extend the basic functionality. There are two primary plugins available: restapi and cooker.
The restapi plugin works with a web based REST Api compatible with the layerindex-web project, as well as the ability to store and retried a the information for one or more files on the disk.
The cooker plugin works by reading the information from the current build project and processing it as if it were a layer index.
TODO:
init.py: Implement local on-disk caching (using the rest api store/load) Implement layer index style query operations on a combined index
common.py: Stop network access if BB_NO_NETWORK or allowed hosts is restricted
cooker.py: Cooker - Implement recipe parsing