summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/providers.py
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2012-01-30 16:25:51 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-02-01 15:08:41 +0000
commit3d2f6d56109fc3ebe9c8e7fe0d84d6cd01a9e2fb (patch)
tree42c2478f7f1c43999e2ac67c43ec982fdfbe5f03 /bitbake/lib/bb/providers.py
parentcf425a13a2283de5483939a9f70b518fb745e9f6 (diff)
downloadpoky-3d2f6d56109fc3ebe9c8e7fe0d84d6cd01a9e2fb.tar.gz
bitbake-layers: use directory name as layer name
It turns out that using the collection name as specified within layer.conf (i.e. what gets added to BBFILE_COLLECTIONS) as a name to refer to the layer is not particularly useful, since layer creators aren't necessarily setting these to a meaningful value - e.g. OE-Core uses "normal", meta-oe uses "openembedded-layer", etc. In any case, BitBake uses the directory name in its list of configured layers in the system information presented upon starting a build, so let's just do the same here and avoid confusion. Also rename the get_append_layer function to get_file_layer since it is in no way specific to bbappends. (Bitbake rev: 35d2c1c618826e961dbf4b9889b829f469346d74) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/providers.py')
0 files changed, 0 insertions, 0 deletions