Add a QA check to verify that scripts do not contain bashisms. The Debian checkbashisms.pl script already covers this sufficiently, as it can distinguish between 3 cases: 1) A script with #! /bin/sh that uses bashisms (BAD) 2) A script with #! /bin/bash that uses bashisms (OK) 3) A script with #! /bin/bash that doesn't use bashisms (OK) At a minimum, an ERROR should be produced if #1 is encountered. We could also issue a WARNING for #3, but that is not as much of an issue.
IMHO, far too invasive/slow to run on every parse. oe-core has verify-bashisms which will run all shell bits in recipes through checkbashisms.
Sorry, maybe it wasn't clear, this was intended to be a QA check for on-target installed files, not bitbake metadata scripts (which is what verify-bashisms appears to be checking?). I found https://bugzilla.yoctoproject.org/show_bug.cgi?id=8851 did that also evaluate the performance impact of a QA check (I didn't find anything like that in the comments)? If not, I can do some evaluation to see what the impact would be on the do_package_qa step.
Ah, right. Reopening.
Bulk move from 4.99 or 0.00 to 5.99
We could put the code in but leave it disabled by default for developers to use as needed.