diff options
author | Ulf Magnusson <ulfalizer@gmail.com> | 2016-10-01 04:47:08 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-10-04 16:29:05 +0100 |
commit | 4dbb0d73dd7458dd67091afb250e4de976e68940 (patch) | |
tree | e204ef1e669a1a9190ec57aa602d4f7d7d026264 /scripts/lib/recipetool/create_npm.py | |
parent | 4c25460c5ae3b7779ced56ce8ed114d512e1f883 (diff) | |
download | poky-4dbb0d73dd7458dd67091afb250e4de976e68940.tar.gz |
package.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: 8443b6f3f25181f5ac49bc25a1387cd05b814376)
Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/recipetool/create_npm.py')
0 files changed, 0 insertions, 0 deletions