summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp/recipes-bsp
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2016-01-18 18:05:21 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-01-19 17:26:15 +0000
commitf0d47a6d9ae773f2c4975679e4dc8cd5ee2700fb (patch)
treeba5e2f2d61c79798914b34ef8687451293696176 /meta-yocto-bsp/recipes-bsp
parent9e867efdc87ced0e2743a3c134f30d2637795654 (diff)
downloadpoky-f0d47a6d9ae773f2c4975679e4dc8cd5ee2700fb.tar.gz
bitbake: Revert "runqueue.py: Ensure one setscene function doesn't mask out another which needs to run"
This reverts commit b22592af8145a8c7c4ada2fa7c1dee2e753eca46. That commit isn't entirely clear about why this change is needed but I do have a usecase where this breaks things. If for example you run "bitbake X -c packagedata" and that packagedata is in sstate, you'd expect this to work. If sstate doesn't contain a do_populate_sysroot for a dependency, you would still expect the command above to succeed and you would not expect it to rebuild that dependency. With the current code, this isn't what happens. The code finds the sstate for do_populate_sysroot missing, this makes the task "uncovered" and this in turn makes it unskippable. The example I found with this was avahi-ui, where it would trigger a build of libdaemon to obtain its populate_sysroot. Since this behaviour seems completely incorrect, revert the older patch and we'll address any issues that crop up as a result. (Bitbake rev: 36a9840a5da17cc14561881fdd6a4f2cb0a75e49) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp/recipes-bsp')
0 files changed, 0 insertions, 0 deletions