diff options
author | Ulf Magnusson <ulfalizer@gmail.com> | 2016-10-01 04:46:53 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-10-04 16:29:04 +0100 |
commit | fc3dc097322e6a02ec67563d05434967478bb34d (patch) | |
tree | bc0b4e2b941fa39ce46ff22cb9b10ef2f6eeab4c /meta/classes/testsdk.bbclass | |
parent | c7d522c71747ebb3382db9bc609125faaa79c844 (diff) | |
download | poky-fc3dc097322e6a02ec67563d05434967478bb34d.tar.gz |
package_rpm.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: f0561ba205723fd7f05c28d501c2c517034b326c)
Signed-off-by: Ulf Magnusson <ulfalizer@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/testsdk.bbclass')
0 files changed, 0 insertions, 0 deletions