summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/fetch2/npm.py
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2016-03-07 18:07:52 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-03-07 17:17:43 +0000
commit26ee4ddc653d97f5c436c66a8504493209e3c65e (patch)
tree8366ab405083d255ef0aca4473aa6f1482429166 /bitbake/lib/bb/fetch2/npm.py
parente43fcdf1e83a95e9ee6382dec042d72213fdc600 (diff)
downloadpoky-26ee4ddc653d97f5c436c66a8504493209e3c65e.tar.gz
image creation: allow overriding .rootfs suffix
By default, the image file name contains ".rootfs" to distinguish the image file from other files created during image building. However, for certain image types (for example, .hddimg) the ".rootfs" suffix is redundant because the type suffix alone already uniquely identifies the main image file (core-image-minimal-intel-corei7-64.hddimg instead of core-image-minimal-intel-corei7-64.rootfs.hddimg). With this change, distros that prefer the shorter image name can override the .rootfs suffix unconditionally with IMAGE_NAME_SUFFIX ?= '' in their distro configuration or with some condition check like this: python () { if <whole-disk image format active>: d.setVar('IMAGE_NAME_SUFFIX', '') } The exact logic when to remove the extra suffix depends on the distro and how it enables its own image type. (From OE-Core rev: 380ee36811939d947024bf78de907e3c071b834f) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/fetch2/npm.py')
0 files changed, 0 insertions, 0 deletions