7 May
2019
7 May
'19
5:09 p.m.
On Sun, 2019-05-05 at 08:50 -0400, Tom Rini wrote:
Conceptually, yes, this is correct. However, the behavior in question has been deployed for so long that I don't feel that we can change it at this point, so I'm going to NAK this. Sorry.
I certainly understand that constraint even though it has caused a fair amount of trouble. For a little more context please see an e-mail I sent to the Buildroot mailing list.[1]
How about as a compromise fw_printenv still prints the same output, but it returns an exit code > 0 when doing so?
Best, Phil
[1]: http://lists.busybox.net/pipermail/buildroot/2019-April/246761.html