diff options
| author |   Mikko Rapeli <mikko.rapeli@bmw.de> | 2017-03-21 12:53:13 +0200 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-03-21 22:43:04 +0000 |
| commit | d8e59d1f840e4282859ad14397d1c06516b8eb11 (patch) | |
| tree | bbd04b3236ffb7b3c53f9eb739e42e5d8c0f0ea7 /meta/classes/sign_rpm.bbclass | |
| parent | 23a12d87a6e82f80f4ccc1a01c707faa89ff7abd (diff) | |
| download | openembedded-core-contrib-d8e59d1f840e4282859ad14397d1c06516b8eb11.tar.gz | |
buildhistory.bbclass: add layer name to source recipe data
It is useful to know which layer provided a given recipe and its
binary packages.
Many projects combine a number of layers and some of them
also provide same recipe names in which case bitbake
can prioritize between them. buildhistory can record
the decision by saving the layer from where the recipe
was taken from.
Also, if a project is split to sub projects which maintain
recipes in different meta layers, then meta layer specific
summaries of e.g. disk usage can be calculated if
source recipes meta layer name is recorded for example in
buildhistory.
If source layer is not in build history, then layer providing
the recipe can be exported from build environment using
'bitbake-layers show-recipes', but it takes a long time to execute
since all recipes are parsed again and requires full source tree
with correct build configuration.
This patch exports the name of layer as configured in BBFILE_COLLECTIONS
append of its layer.conf. 'bitbake-layers show-recipes' exports the
meta layers directory path name. For several open source layers
these are different, e.g. meta-openembedded/meta-perl/conf/layer.conf
is perl-layer, poky/meta/conf/layer.conf is core,
poky/meta-skeleton/conf/layer.conf is skeleton etc.
Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/classes/sign_rpm.bbclass')
0 files changed, 0 insertions, 0 deletions