summaryrefslogtreecommitdiff
path: root/meta/classes/python3-dir.bbclass
diff options
context:
space:
mode:
authorUlf Magnusson <ulfalizer@gmail.com>2016-10-01 04:47:04 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-10-03 15:46:21 +0100
commit33611b69c221cf875eba1c7cb599c256825ae470 (patch)
tree6a04ffc92dcec170f7717ac387069bbd1a81357e /meta/classes/python3-dir.bbclass
parent21969c3d1397e0a11a8cb9dad8ce3469ee655f57 (diff)
downloadopenembedded-core-33611b69c221cf875eba1c7cb599c256825ae470.tar.gz
openembedded-core-33611b69c221cf875eba1c7cb599c256825ae470.tar.bz2
openembedded-core-33611b69c221cf875eba1c7cb599c256825ae470.zip
sstate.bbclass: Use bb.fatal() instead of raising FuncFailed
This sets a good example and avoids unnecessarily contributing to perceived complexity and cargo culting. Motivating quote below: < kergoth> the *original* intent was for the function/task to error via whatever appropriate means, bb.fatal, whatever, and funcfailed was what you'd catch if you were calling exec_func/exec_task. that is, it's what those functions raise, not what metadata functions should be raising < kergoth> it didn't end up being used that way < kergoth> but there's really never a reason to raise it yourself FuncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/python3-dir.bbclass')
0 files changed, 0 insertions, 0 deletions