diff options
author | Ulf Magnusson <ulfalizer@gmail.com> | 2016-10-01 04:46:54 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-10-03 15:46:21 +0100 |
commit | e507cb978fd52164beb28324933cb3d5e368c3ab (patch) | |
tree | 3f8ec82a4a4a10ffc4780b2162ceba4d81f169a7 /meta/recipes-bsp/apmd | |
parent | f0561ba205723fd7f05c28d501c2c517034b326c (diff) | |
download | openembedded-core-e507cb978fd52164beb28324933cb3d5e368c3ab.tar.gz openembedded-core-e507cb978fd52164beb28324933cb3d5e368c3ab.tar.bz2 openembedded-core-e507cb978fd52164beb28324933cb3d5e368c3ab.zip |
useradd-staticids.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/recipes-bsp/apmd')
0 files changed, 0 insertions, 0 deletions