diff options
author | Ulf Magnusson <ulfalizer@gmail.com> | 2016-10-01 04:47:02 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-10-04 16:29:04 +0100 |
commit | fadc4fc746c09228c5b52b0e484664e73d9fb87e (patch) | |
tree | 84399ecd3970860c347dc9edb91787fb94f39612 /meta/recipes-sato | |
parent | 823acf80373852cbc5a26807165ffbcc397b0a3d (diff) | |
download | poky-fadc4fc746c09228c5b52b0e484664e73d9fb87e.tar.gz |
gtk-immodules-cache.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.
(From OE-Core rev: 11a2f932073635f9680470cd69216cecf7ed0c37)
Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-sato')
0 files changed, 0 insertions, 0 deletions