I was never a fan of set -e. I prefer to do my own error handling. But, I never understood why pipefail wasn't the default. A failure is a failure. I would like to know about it!
Yeah. Using yocto, I know what I want and can do it in Linux. But, "how make yocto do it" becomes an entirely different thing. It would be nice to have a simple container->image pipeline.
Right now, the most common target we have at work is variscite imx6,7 and 8. Nxp has leaned heavily into yocto. To be clear, this would be an outside of work thing, but I'll probably yoke one of our dev boards.
I was never a fan of
set -e. I prefer to do my own error handling. But, I never understood why pipefail wasn't the default. A failure is a failure. I would like to know about it!